Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cd2e76748eb6916dfef15130c4a1dea03dc5fde2627ded6bb86d498ce1b2ac9

Tx prefix hash: fc9176318ab9e4a670d48cc0c170433009ecf09df92b83f16a82b82ba7086a81
Tx public key: 572d0dc66d8e5436689189865f219c333b0a9efd970aff193b2f3215c7ca43b2
Timestamp: 1727112558 Timestamp [UCT]: 2024-09-23 17:29:18 Age [y:d:h:m:s]: 00:198:00:04:17
Block: 1116521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141328 RingCT/type: yes/0
Extra: 01572d0dc66d8e5436689189865f219c333b0a9efd970aff193b2f3215c7ca43b202110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc1dda8c65645a993509f3e76f3037c81c3cf45268fbe4f7dbf65fd04e6001c6 0.600000000000 1597036 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": 1116531, "vin": [ { "gen": { "height": 1116521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc1dda8c65645a993509f3e76f3037c81c3cf45268fbe4f7dbf65fd04e6001c6" } } ], "extra": [ 1, 87, 45, 13, 198, 109, 142, 84, 54, 104, 145, 137, 134, 95, 33, 156, 51, 59, 10, 158, 253, 151, 10, 255, 25, 59, 47, 50, 21, 199, 202, 67, 178, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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