Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6f9a4280b9235d23fa7a18a7c5e296cb3570072e757fa3c7cace70ba2f8570cd

Tx prefix hash: bee0f959f6e3cf2ce9be5f66df708216d9c64ccecfa7c411cce0b3681077419a
Tx public key: 333e352889e905a5c6fdeeab8b7714dd28812df19eb8457e6076ab218785958f
Timestamp: 1733501755 Timestamp [UCT]: 2024-12-06 16:15:55 Age [y:d:h:m:s]: 00:118:05:00:30
Block: 1169389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84275 RingCT/type: yes/0
Extra: 01333e352889e905a5c6fdeeab8b7714dd28812df19eb8457e6076ab218785958f021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27c913b610129eb749c5cf69299909d96d733f65a5ac0aa00618a728ae359c3d 0.600000000000 1655106 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1169399, "vin": [ { "gen": { "height": 1169389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27c913b610129eb749c5cf69299909d96d733f65a5ac0aa00618a728ae359c3d" } } ], "extra": [ 1, 51, 62, 53, 40, 137, 233, 5, 165, 198, 253, 238, 171, 139, 119, 20, 221, 40, 129, 45, 241, 158, 184, 69, 126, 96, 118, 171, 33, 135, 133, 149, 143, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8