Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38dba198fb48507600a718b88326761ef2f648b3c9c9397e1ab2334b4fe35f83

Tx prefix hash: 5026a839c132157a251975f0784ecb52843cd95e3d22b5f1fa714a378972da27
Tx public key: b8ce6c50e96ac641929d13d0879b4358f24abef0bc0bea9d68d4a4103e1f52c8
Timestamp: 1686106840 Timestamp [UCT]: 2023-06-07 03:00:40 Age [y:d:h:m:s]: 02:124:05:54:47
Block: 776805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 608527 RingCT/type: yes/0
Extra: 01b8ce6c50e96ac641929d13d0879b4358f24abef0bc0bea9d68d4a4103e1f52c8021100000002faf35c9c000000000000000000

1 output(s) for total of 1.637279152000 dcy

stealth address amount amount idx
00: b8237790f6ce0e64e9e54d30ca220b241545e71ecfe956edbee13b0314339563 1.637279152000 1226368 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": 776815, "vin": [ { "gen": { "height": 776805 } } ], "vout": [ { "amount": 1637279152, "target": { "key": "b8237790f6ce0e64e9e54d30ca220b241545e71ecfe956edbee13b0314339563" } } ], "extra": [ 1, 184, 206, 108, 80, 233, 106, 198, 65, 146, 157, 19, 208, 135, 155, 67, 88, 242, 74, 190, 240, 188, 11, 234, 157, 104, 212, 164, 16, 62, 31, 82, 200, 2, 17, 0, 0, 0, 2, 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