Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05770283b92726d3a64616051819ee7c6b872945f33dcc1ad944ee05735ab5cb

Tx prefix hash: 9cb02245ca00a7288a4a05f200b41fb9c57a18f25471d2cd23db495afc409339
Tx public key: 58f58d72afff9d3a8b536115d238b10aa97e0319d1374c4be8efd6d8017f7526
Timestamp: 1711498534 Timestamp [UCT]: 2024-03-27 00:15:34 Age [y:d:h:m:s]: 01:081:07:33:05
Block: 987100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318998 RingCT/type: yes/0
Extra: 0158f58d72afff9d3a8b536115d238b10aa97e0319d1374c4be8efd6d8017f752602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa9b8624430253f07d1631f1995be5fd67d726f25ac7871f64fc306e0d14a197 0.600000000000 1447341 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": 987110, "vin": [ { "gen": { "height": 987100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa9b8624430253f07d1631f1995be5fd67d726f25ac7871f64fc306e0d14a197" } } ], "extra": [ 1, 88, 245, 141, 114, 175, 255, 157, 58, 139, 83, 97, 21, 210, 56, 177, 10, 169, 126, 3, 25, 209, 55, 76, 75, 232, 239, 214, 216, 1, 127, 117, 38, 2, 17, 0, 0, 0, 5, 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