Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80565d49aa47b3820f6b19151a8740b4e21256c689aaf68b572283a014348248

Tx prefix hash: 119df8eea37bad94f6bb94489e992ac8c80985fd3dfdd5350b7115a1d5f18443
Tx public key: f2e5d1207cf75c8d52bda6fa4a573e015f1dc32c4c115e44983ec7de16b0d0d1
Timestamp: 1698674764 Timestamp [UCT]: 2023-10-30 14:06:04 Age [y:d:h:m:s]: 01:203:10:47:50
Block: 880977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406431 RingCT/type: yes/0
Extra: 01f2e5d1207cf75c8d52bda6fa4a573e015f1dc32c4c115e44983ec7de16b0d0d1021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.739532900000 dcy

stealth address amount amount idx
00: 5e67969bf5ca644d8d7c0a850a6ccb9b2eb889ebd28dc9bce96ecae85a9e947f 0.739532900000 1336547 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": 880987, "vin": [ { "gen": { "height": 880977 } } ], "vout": [ { "amount": 739532900, "target": { "key": "5e67969bf5ca644d8d7c0a850a6ccb9b2eb889ebd28dc9bce96ecae85a9e947f" } } ], "extra": [ 1, 242, 229, 209, 32, 124, 247, 92, 141, 82, 189, 166, 250, 74, 87, 62, 1, 95, 29, 195, 44, 76, 17, 94, 68, 152, 62, 199, 222, 22, 176, 208, 209, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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