Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4639d1613a416ec48a314c2e444eb9f1cf0ee5883aa9e3dbdc3d143c8136c845

Tx prefix hash: ab9eedc14444c64b82607cb2d331a322ec9867aa65b453664500643dac6c59d7
Tx public key: 15d8b9adf9f960986fe660fff44f080ee2b920b295134117407b7fbfcc0878dd
Timestamp: 1719605890 Timestamp [UCT]: 2024-06-28 20:18:10 Age [y:d:h:m:s]: 00:321:01:57:31
Block: 1054271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229464 RingCT/type: yes/0
Extra: 0115d8b9adf9f960986fe660fff44f080ee2b920b295134117407b7fbfcc0878dd02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3f5a426e10f4d3d61727d999a9abd7fcb3eac8dea2f49507753eb2e62d36115 0.600000000000 1524632 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": 1054281, "vin": [ { "gen": { "height": 1054271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3f5a426e10f4d3d61727d999a9abd7fcb3eac8dea2f49507753eb2e62d36115" } } ], "extra": [ 1, 21, 216, 185, 173, 249, 249, 96, 152, 111, 230, 96, 255, 244, 79, 8, 14, 226, 185, 32, 178, 149, 19, 65, 23, 64, 123, 127, 191, 204, 8, 120, 221, 2, 17, 0, 0, 0, 1, 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