Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ec1a4bbd8eaaabf015c28b839cade96465cc0e2e6380572c934607bbd74dce8

Tx prefix hash: a56bbfcd376711679041a1b88b31bbf0be0eb94f5e6a98ab14010878cb4a369a
Tx public key: 4409f0caa50338f18035d17dbf0a809fb2b35bf925e777673a9355c8e9f78a02
Timestamp: 1716496729 Timestamp [UCT]: 2024-05-23 20:38:49 Age [y:d:h:m:s]: 00:336:08:13:15
Block: 1028511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240408 RingCT/type: yes/0
Extra: 014409f0caa50338f18035d17dbf0a809fb2b35bf925e777673a9355c8e9f78a020211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b4687e12c657b6735232dc4c432e687ca2c3d8ef0b8ef880a38622fd2c05d4a 0.600000000000 1496504 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": 1028521, "vin": [ { "gen": { "height": 1028511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b4687e12c657b6735232dc4c432e687ca2c3d8ef0b8ef880a38622fd2c05d4a" } } ], "extra": [ 1, 68, 9, 240, 202, 165, 3, 56, 241, 128, 53, 209, 125, 191, 10, 128, 159, 178, 179, 91, 249, 37, 231, 119, 103, 58, 147, 85, 200, 233, 247, 138, 2, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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