Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d5532cde5c30446c402751e064a4763f5563dfcc414a1ad8d949f3e3916d7f1

Tx prefix hash: ee05dcf3376d147a56041745df07e1adcf0314afd1875026eace8e23b5d29405
Tx public key: 3f3f353d067a1ac3ffe4b472e13becd58a5965ae41b5b87a527f54b074930aee
Timestamp: 1709889359 Timestamp [UCT]: 2024-03-08 09:15:59 Age [y:d:h:m:s]: 01:067:00:29:32
Block: 973744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308918 RingCT/type: yes/0
Extra: 013f3f353d067a1ac3ffe4b472e13becd58a5965ae41b5b87a527f54b074930aee02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e765cf0e93ca4e6a94e937e482f711e9bbdb78260469ee138a3b40f15fee9232 0.600000000000 1433683 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": 973754, "vin": [ { "gen": { "height": 973744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e765cf0e93ca4e6a94e937e482f711e9bbdb78260469ee138a3b40f15fee9232" } } ], "extra": [ 1, 63, 63, 53, 61, 6, 122, 26, 195, 255, 228, 180, 114, 225, 59, 236, 213, 138, 89, 101, 174, 65, 181, 184, 122, 82, 127, 84, 176, 116, 147, 10, 238, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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