Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9981c50a26b04a719fe61e3a4c7a4eb6060e7a19f1b2e638cb98b5aa280012c8

Tx prefix hash: 9ee4587441c6ce4943f8e8aea3511dbc15d8fa00afc6b9630b1982075c9e3f60
Tx public key: e0c62161f93c7a0c1c0954441017e6f0c52367b253e1ad33a154cbced8a203e9
Timestamp: 1719563773 Timestamp [UCT]: 2024-06-28 08:36:13 Age [y:d:h:m:s]: 01:134:03:38:53
Block: 1053935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354422 RingCT/type: yes/0
Extra: 01e0c62161f93c7a0c1c0954441017e6f0c52367b253e1ad33a154cbced8a203e902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfeb0d09d2c4f568964e00e580b84caa7bd874a0866e23891b51c85b9141b710 0.600000000000 1524290 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": 1053945, "vin": [ { "gen": { "height": 1053935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfeb0d09d2c4f568964e00e580b84caa7bd874a0866e23891b51c85b9141b710" } } ], "extra": [ 1, 224, 198, 33, 97, 249, 60, 122, 12, 28, 9, 84, 68, 16, 23, 230, 240, 197, 35, 103, 178, 83, 225, 173, 51, 161, 84, 203, 206, 216, 162, 3, 233, 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