Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 322ee0840301fc35e8f4e0f7284a4aa5c5dacaeabe7af7c801eb0a1702dbaab5

Tx prefix hash: fe957ac1c5cd7d25be806d362bdc6cbb7a0f493e3ed4533c05e085e300c0c43a
Tx public key: db4f1264249ca0995538b739fa6698617bd55e47d78f8e59d7561ae0417d666d
Timestamp: 1721414127 Timestamp [UCT]: 2024-07-19 18:35:27 Age [y:d:h:m:s]: 00:310:01:55:29
Block: 1069285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221572 RingCT/type: yes/0
Extra: 01db4f1264249ca0995538b739fa6698617bd55e47d78f8e59d7561ae0417d666d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e770da6208a0ebdc6c9bc6345d569bef87a044f30e4f5ef9a72c630bb8bcd6c0 0.600000000000 1540654 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": 1069295, "vin": [ { "gen": { "height": 1069285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e770da6208a0ebdc6c9bc6345d569bef87a044f30e4f5ef9a72c630bb8bcd6c0" } } ], "extra": [ 1, 219, 79, 18, 100, 36, 156, 160, 153, 85, 56, 183, 57, 250, 102, 152, 97, 123, 213, 94, 71, 215, 143, 142, 89, 215, 86, 26, 224, 65, 125, 102, 109, 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