Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b987d0ea655fc9204a0fef68367487d93fe3e480665b7119aa504355975bdcc

Tx prefix hash: 64d85109a50ebd1a8241bd37d9ee8b2472c151f2185f9eadcba675320e3aa0aa
Tx public key: 808a029cb4995c8e0ccdd3f15ab5fb3aa713108b8ccca39f83a292af862953e2
Timestamp: 1713983449 Timestamp [UCT]: 2024-04-24 18:30:49 Age [y:d:h:m:s]: 00:351:14:14:06
Block: 1007674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251350 RingCT/type: yes/0
Extra: 01808a029cb4995c8e0ccdd3f15ab5fb3aa713108b8ccca39f83a292af862953e20211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08e137889e598e08f75a0a235a9a0cd67d0ba4d6f713ff035d1e3580ef443bbe 0.600000000000 1469092 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": 1007684, "vin": [ { "gen": { "height": 1007674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08e137889e598e08f75a0a235a9a0cd67d0ba4d6f713ff035d1e3580ef443bbe" } } ], "extra": [ 1, 128, 138, 2, 156, 180, 153, 92, 142, 12, 205, 211, 241, 90, 181, 251, 58, 167, 19, 16, 139, 140, 204, 163, 159, 131, 162, 146, 175, 134, 41, 83, 226, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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