Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cec3046783e59f9c5109bcb3f46b75043307f6f813d9bad23e1ff3a8beb51fc9

Tx prefix hash: 0fc32fc7c4c3b8e7a3fd2738a837c9eae8f9961da449ad020d4c1bed10222a72
Tx public key: 3613b8b05641d0360cc2a6646e5f7f24ab84e38bccda6056af79bba4d5409e9a
Timestamp: 1726263458 Timestamp [UCT]: 2024-09-13 21:37:38 Age [y:d:h:m:s]: 00:112:13:32:19
Block: 1109473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80512 RingCT/type: yes/0
Extra: 013613b8b05641d0360cc2a6646e5f7f24ab84e38bccda6056af79bba4d5409e9a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e2d54fa05722dead61973049fa3aefe4221f92d4a3a31bc026202997d574bb7 0.600000000000 1587744 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": 1109483, "vin": [ { "gen": { "height": 1109473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e2d54fa05722dead61973049fa3aefe4221f92d4a3a31bc026202997d574bb7" } } ], "extra": [ 1, 54, 19, 184, 176, 86, 65, 208, 54, 12, 194, 166, 100, 110, 95, 127, 36, 171, 132, 227, 139, 204, 218, 96, 86, 175, 121, 187, 164, 213, 64, 158, 154, 2, 17, 0, 0, 0, 3, 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