Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e533a1127941f063bb31fb5167a59efbaf345af7915287533e4c0112106ccc1

Tx prefix hash: 74eeca5db01cc7a9f108fe83dea1fc7448ca2178fd8a301421dc9990c60650e1
Tx public key: 71d8d9e9c8e12cd736c31a59c3c259c6ea219924a174cec80345ecf8cfa50496
Timestamp: 1738031722 Timestamp [UCT]: 2025-01-28 02:35:22 Age [y:d:h:m:s]: 00:327:14:03:06
Block: 1206639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231925 RingCT/type: yes/0
Extra: 0171d8d9e9c8e12cd736c31a59c3c259c6ea219924a174cec80345ecf8cfa50496021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08ae90aa604db34b389f20a211b9d7ba0eb9a89f8b8e2fe7919c253b68d22c60 0.600000000000 1693350 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": 1206649, "vin": [ { "gen": { "height": 1206639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08ae90aa604db34b389f20a211b9d7ba0eb9a89f8b8e2fe7919c253b68d22c60" } } ], "extra": [ 1, 113, 216, 217, 233, 200, 225, 44, 215, 54, 195, 26, 89, 195, 194, 89, 198, 234, 33, 153, 36, 161, 116, 206, 200, 3, 69, 236, 248, 207, 165, 4, 150, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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