Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce89d8b22db21f958f46074713d052382bcf9d6d97904f3fcd7e244391e77650

Tx prefix hash: 11c671ac356e6984e268556f2dcaf3b16d82a67ebf788fcb383dd52e8a2e8f67
Tx public key: 7cf8f3d5a0766c3d86fb0eadd0d1daa51b59a9361a20faa95fbfbe7461d22e8e
Timestamp: 1694531800 Timestamp [UCT]: 2023-09-12 15:16:40 Age [y:d:h:m:s]: 01:191:08:05:29
Block: 846592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397844 RingCT/type: yes/0
Extra: 017cf8f3d5a0766c3d86fb0eadd0d1daa51b59a9361a20faa95fbfbe7461d22e8e021100000007faf35c9c000000000000000000

1 output(s) for total of 0.961367262000 dcy

stealth address amount amount idx
00: e451db69c4a16110b2e501deb8c7e26bea121554f3b314e78581e9ac3d96ca03 0.961367262000 1300062 of 0

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": 846602, "vin": [ { "gen": { "height": 846592 } } ], "vout": [ { "amount": 961367262, "target": { "key": "e451db69c4a16110b2e501deb8c7e26bea121554f3b314e78581e9ac3d96ca03" } } ], "extra": [ 1, 124, 248, 243, 213, 160, 118, 108, 61, 134, 251, 14, 173, 208, 209, 218, 165, 27, 89, 169, 54, 26, 32, 250, 169, 95, 191, 190, 116, 97, 210, 46, 142, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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