Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 940158f64ec563061c72bf242d177cee91a8f6b5c40d94410da495f13aabb0b5

Tx prefix hash: 96f2d03209f0b3b09f7ce1212144f00df8f4750822870e438b50f5150637468f
Tx public key: c991ff9f3e529e78aa4cae8e788f4e121ef27c88040720e993bca9ae11d4832b
Timestamp: 1738292831 Timestamp [UCT]: 2025-01-31 03:07:11 Age [y:d:h:m:s]: 00:141:23:37:13
Block: 1208792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101362 RingCT/type: yes/0
Extra: 01c991ff9f3e529e78aa4cae8e788f4e121ef27c88040720e993bca9ae11d4832b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b23e954f2d0bb5b8eb57ad2794b61149798dd16934fadcef870b9250ae12b35b 0.600000000000 1695527 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": 1208802, "vin": [ { "gen": { "height": 1208792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b23e954f2d0bb5b8eb57ad2794b61149798dd16934fadcef870b9250ae12b35b" } } ], "extra": [ 1, 201, 145, 255, 159, 62, 82, 158, 120, 170, 76, 174, 142, 120, 143, 78, 18, 30, 242, 124, 136, 4, 7, 32, 233, 147, 188, 169, 174, 17, 212, 131, 43, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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