Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd0f690d81f30ae60c447117cd38cc15bd38b24c9c634eae8137ab30505e0786

Tx prefix hash: bf631480afcbc9418c7d66aacf19a1ed6c933eab03d4e5e60a281d32763b838e
Tx public key: 6b39fc529dfbf26737f317bfcc8db4d4060a9998b211e0671394636f6156310d
Timestamp: 1674940313 Timestamp [UCT]: 2023-01-28 21:11:53 Age [y:d:h:m:s]: 02:120:01:34:25
Block: 684864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607482 RingCT/type: yes/0
Extra: 016b39fc529dfbf26737f317bfcc8db4d4060a9998b211e0671394636f6156310d0211000000025029cbac000000000000000000

1 output(s) for total of 3.301879371000 dcy

stealth address amount amount idx
00: e6c2b0f5c81ea65415a78e91d79f7303a736e2eb2b79a2e0e890019f2ca781b7 3.301879371000 1127143 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": 684874, "vin": [ { "gen": { "height": 684864 } } ], "vout": [ { "amount": 3301879371, "target": { "key": "e6c2b0f5c81ea65415a78e91d79f7303a736e2eb2b79a2e0e890019f2ca781b7" } } ], "extra": [ 1, 107, 57, 252, 82, 157, 251, 242, 103, 55, 243, 23, 191, 204, 141, 180, 212, 6, 10, 153, 152, 178, 17, 224, 103, 19, 148, 99, 111, 97, 86, 49, 13, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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