Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ecf345ef5da225095439226a55d3bc26345b3eecd2c527b0bb362d7cd791dae

Tx prefix hash: 272b0a63f36252b6d91e5870315535baaaaedd9654b0921f535f36375596d9b8
Tx public key: 5d498f5c2c7187d8ec63e5780e68e88645999b4a9e5ba08913d20a58b6479218
Timestamp: 1716037810 Timestamp [UCT]: 2024-05-18 13:10:10 Age [y:d:h:m:s]: 00:318:19:53:35
Block: 1024711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227872 RingCT/type: yes/0
Extra: 015d498f5c2c7187d8ec63e5780e68e88645999b4a9e5ba08913d20a58b647921802110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d879c247c0c72c93c717dd89c03a5a1733f4fbf7e18eb36f783b1c441fd259c7 0.600000000000 1490670 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": 1024721, "vin": [ { "gen": { "height": 1024711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d879c247c0c72c93c717dd89c03a5a1733f4fbf7e18eb36f783b1c441fd259c7" } } ], "extra": [ 1, 93, 73, 143, 92, 44, 113, 135, 216, 236, 99, 229, 120, 14, 104, 232, 134, 69, 153, 155, 74, 158, 91, 160, 137, 19, 210, 10, 88, 182, 71, 146, 24, 2, 17, 0, 0, 0, 9, 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