Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a1e35633ec39ff9593d3d761ac74dc315d054992ea8324ea589e6c11b9b7c8

Tx prefix hash: 9a2c94d4169f49570b8c1048d5ffb2fa52c59d34f94c63adeb7f4a8466147f04
Tx public key: 4325e858187c67a5511f9cdc4b979778155b9249b157f9e36d5e15da9e72c363
Timestamp: 1707441612 Timestamp [UCT]: 2024-02-09 01:20:12 Age [y:d:h:m:s]: 01:131:02:45:52
Block: 953432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354660 RingCT/type: yes/0
Extra: 014325e858187c67a5511f9cdc4b979778155b9249b157f9e36d5e15da9e72c36302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9241767bd577e83c4eec13c46600a9ebdaa8a0bd036ab3b1fa17f4f2b3a3e6a 0.600000000000 1412638 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": 953442, "vin": [ { "gen": { "height": 953432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9241767bd577e83c4eec13c46600a9ebdaa8a0bd036ab3b1fa17f4f2b3a3e6a" } } ], "extra": [ 1, 67, 37, 232, 88, 24, 124, 103, 165, 81, 31, 156, 220, 75, 151, 151, 120, 21, 91, 146, 73, 177, 87, 249, 227, 109, 94, 21, 218, 158, 114, 195, 99, 2, 17, 0, 0, 0, 4, 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