Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b2087eac199c942cd274a8bb4d0f4a7958e066026939576254280f913b00d48

Tx prefix hash: 38fb01ee010957bd35ba4b4e3b33b985058de85934ecb789565b2e9f538d370a
Tx public key: 8a4c4018c5a769702206ab58cfdb58df95e43e80e85fca0862e957eb053cccb7
Timestamp: 1717603665 Timestamp [UCT]: 2024-06-05 16:07:45 Age [y:d:h:m:s]: 00:284:10:40:56
Block: 1037691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203283 RingCT/type: yes/0
Extra: 018a4c4018c5a769702206ab58cfdb58df95e43e80e85fca0862e957eb053cccb702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d38ebc7fd7e229de132ec5fad0c426160aac3f3b11b2ffd4f7fe7d2c3fd7692 0.600000000000 1506244 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": 1037701, "vin": [ { "gen": { "height": 1037691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d38ebc7fd7e229de132ec5fad0c426160aac3f3b11b2ffd4f7fe7d2c3fd7692" } } ], "extra": [ 1, 138, 76, 64, 24, 197, 167, 105, 112, 34, 6, 171, 88, 207, 219, 88, 223, 149, 228, 62, 128, 232, 95, 202, 8, 98, 233, 87, 235, 5, 60, 204, 183, 2, 17, 0, 0, 0, 1, 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