Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fc395f83ea2714740b4a14947d38df407c0e27be07d146e6ee78b265b80c8e1

Tx prefix hash: 13a22cd0d1e5501fde36a73cbca8a372ca509479e522e54aa43d965e4fae4933
Tx public key: 191b7e9f5d6df88a1be290124a9f3868805f3edbe2157623c84c6ca14f9f26c8
Timestamp: 1713135190 Timestamp [UCT]: 2024-04-14 22:53:10 Age [y:d:h:m:s]: 00:336:13:33:23
Block: 1000624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240645 RingCT/type: yes/0
Extra: 01191b7e9f5d6df88a1be290124a9f3868805f3edbe2157623c84c6ca14f9f26c802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ed780cea8e9dfc7809b72a91a92347495da7962504b5aa660a2cf8296802c47 0.600000000000 1461122 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": 1000634, "vin": [ { "gen": { "height": 1000624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ed780cea8e9dfc7809b72a91a92347495da7962504b5aa660a2cf8296802c47" } } ], "extra": [ 1, 25, 27, 126, 159, 93, 109, 248, 138, 27, 226, 144, 18, 74, 159, 56, 104, 128, 95, 62, 219, 226, 21, 118, 35, 200, 76, 108, 161, 79, 159, 38, 200, 2, 17, 0, 0, 0, 2, 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