Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a69234aea1fb1417a02fe845176eae3c69f0459370c196e3342e834b992c7316

Tx prefix hash: fa671cab3ecb9eaefc7d1d828795922bfdee5c0effeadada8b6ac0eac0b61392
Tx public key: 8155afdf8ed22661d4d7f1d1679f280a3242abc7fef44302ac1c6846c79767b9
Timestamp: 1726004115 Timestamp [UCT]: 2024-09-10 21:35:15 Age [y:d:h:m:s]: 00:189:22:21:51
Block: 1107340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135586 RingCT/type: yes/0
Extra: 018155afdf8ed22661d4d7f1d1679f280a3242abc7fef44302ac1c6846c79767b9021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21d2d2af42a3613d3a1a93cfc763f3bfbdf30460ddb78efd6692b49c260bdcc3 0.600000000000 1584951 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": 1107350, "vin": [ { "gen": { "height": 1107340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21d2d2af42a3613d3a1a93cfc763f3bfbdf30460ddb78efd6692b49c260bdcc3" } } ], "extra": [ 1, 129, 85, 175, 223, 142, 210, 38, 97, 212, 215, 241, 209, 103, 159, 40, 10, 50, 66, 171, 199, 254, 244, 67, 2, 172, 28, 104, 70, 199, 151, 103, 185, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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