Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5e1dd3f5c4572a38675a2d9fa53eed9b094e4b8a4eb413013795b526438367a

Tx prefix hash: 71c8fc23a5a1a2b3cbbee1701ec789c02e5750b93e4dc7521de87e1fa6f1b70e
Tx public key: 31c6f3229a51e764a05438046d4fca3c72628c0cd2aa3dea934a934b4b1bd379
Timestamp: 1704260260 Timestamp [UCT]: 2024-01-03 05:37:40 Age [y:d:h:m:s]: 01:126:19:52:18
Block: 927052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351774 RingCT/type: yes/0
Extra: 0131c6f3229a51e764a05438046d4fca3c72628c0cd2aa3dea934a934b4b1bd37902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3b4689d5b78aa185016fc2c905262ce2e76112ad6e8ba30100df516a2e86281 0.600000000000 1384852 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": 927062, "vin": [ { "gen": { "height": 927052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3b4689d5b78aa185016fc2c905262ce2e76112ad6e8ba30100df516a2e86281" } } ], "extra": [ 1, 49, 198, 243, 34, 154, 81, 231, 100, 160, 84, 56, 4, 109, 79, 202, 60, 114, 98, 140, 12, 210, 170, 61, 234, 147, 74, 147, 75, 75, 27, 211, 121, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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