Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06e0eb495115e86b45900dce94cdbb7c08f7259787c8be022c0f8349e9934900

Tx prefix hash: 4ea8dc7aad9036a88e6465b086308ec23458a7c3e956ce1017a99bcbcb2335be
Tx public key: 7fc719c944edcd4fd2849610ac59a6a43126e5f6914d5b7794e1bdf67641d093
Timestamp: 1723083528 Timestamp [UCT]: 2024-08-08 02:18:48 Age [y:d:h:m:s]: 00:251:04:18:43
Block: 1083116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179416 RingCT/type: yes/0
Extra: 017fc719c944edcd4fd2849610ac59a6a43126e5f6914d5b7794e1bdf67641d09302110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bcdbe874bc0e0bdf99c734ce7e57a1b3a1db5b5ea29b2230cbe8a3fb0d684ff 0.600000000000 1556951 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": 1083126, "vin": [ { "gen": { "height": 1083116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bcdbe874bc0e0bdf99c734ce7e57a1b3a1db5b5ea29b2230cbe8a3fb0d684ff" } } ], "extra": [ 1, 127, 199, 25, 201, 68, 237, 205, 79, 210, 132, 150, 16, 172, 89, 166, 164, 49, 38, 229, 246, 145, 77, 91, 119, 148, 225, 189, 246, 118, 65, 208, 147, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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