Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29b25895fb282bedfe88e3e3c5164715aabfc90939d81a3ac0961ccd41564a95

Tx prefix hash: ff6ae0bd36531b7ae46dc508997dce87d109c53f0834d2cb1f82281a11bcf8e5
Tx public key: cfe44eb7f8cf4f976ae177d493b4f5f77ec824b621b08d3cf83fedbfd31e5865
Timestamp: 1703009429 Timestamp [UCT]: 2023-12-19 18:10:29 Age [y:d:h:m:s]: 00:340:04:26:18
Block: 916701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243571 RingCT/type: yes/0
Extra: 01cfe44eb7f8cf4f976ae177d493b4f5f77ec824b621b08d3cf83fedbfd31e586502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b9ab87aa5f3688f0a9d11b92e3510aab9bba207d0a34f794e7d2f7e7f3cf6d0 0.600000000000 1374261 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": 916711, "vin": [ { "gen": { "height": 916701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b9ab87aa5f3688f0a9d11b92e3510aab9bba207d0a34f794e7d2f7e7f3cf6d0" } } ], "extra": [ 1, 207, 228, 78, 183, 248, 207, 79, 151, 106, 225, 119, 212, 147, 180, 245, 247, 126, 200, 36, 182, 33, 176, 141, 60, 248, 63, 237, 191, 211, 30, 88, 101, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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