Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cf126f9a93d37d8ed31d52410f19d3a702bd9fc20d8442c297cdd382fbc64e1

Tx prefix hash: 4b2dfcb4a0fd460fe55844b91bb3ee4f4b30ea9450ced645e32bf6f1aa7ed689
Tx public key: 51847a4d159b60c2be50a0122ace66a9b6df4ee198820c7b06f87ce5fe6de4c9
Timestamp: 1705574328 Timestamp [UCT]: 2024-01-18 10:38:48 Age [y:d:h:m:s]: 01:037:06:32:04
Block: 937940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287696 RingCT/type: yes/0
Extra: 0151847a4d159b60c2be50a0122ace66a9b6df4ee198820c7b06f87ce5fe6de4c902110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c5eb967e1ae28fe2c4c12dc3f29dc022abf215b24adb9b3f1bdc9d1f1ba9ba5 0.600000000000 1396004 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": 937950, "vin": [ { "gen": { "height": 937940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c5eb967e1ae28fe2c4c12dc3f29dc022abf215b24adb9b3f1bdc9d1f1ba9ba5" } } ], "extra": [ 1, 81, 132, 122, 77, 21, 155, 96, 194, 190, 80, 160, 18, 42, 206, 102, 169, 182, 223, 78, 225, 152, 130, 12, 123, 6, 248, 124, 229, 254, 109, 228, 201, 2, 17, 0, 0, 0, 13, 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