Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cfd7608a828e8bf10b56820f87538db2781cf23002a20f6f9893172ec268ef4

Tx prefix hash: 3e466925c4212d963f46996c273d4e109dc0cc589bcc631b76a5c39c8ecc15f6
Tx public key: 4d0e63f394e20a9ba82041ffe957ef7ebdf07c0fc6fc888a431f32d4efc28f9d
Timestamp: 1706845375 Timestamp [UCT]: 2024-02-02 03:42:55 Age [y:d:h:m:s]: 01:087:00:59:35
Block: 948484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323301 RingCT/type: yes/0
Extra: 014d0e63f394e20a9ba82041ffe957ef7ebdf07c0fc6fc888a431f32d4efc28f9d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 36fdbc1332cd24cd26105f241fb38245ac29dfdc169be33bf9c7beed2fc7b051 0.600010000000 1406900 of 0

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": 948494, "vin": [ { "gen": { "height": 948484 } } ], "vout": [ { "amount": 600010000, "target": { "key": "36fdbc1332cd24cd26105f241fb38245ac29dfdc169be33bf9c7beed2fc7b051" } } ], "extra": [ 1, 77, 14, 99, 243, 148, 226, 10, 155, 168, 32, 65, 255, 233, 87, 239, 126, 189, 240, 124, 15, 198, 252, 136, 138, 67, 31, 50, 212, 239, 194, 143, 157, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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