Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 523812d630515bcaac064a19a728cfe9949ee052fdd06c5b19b8522915920903

Tx prefix hash: 51ae42b20936c1ed6dce72cd8cb20b29236b3ed3b391aa73129b4365b13937ff
Tx public key: c82281ccf72439c295d37138e4a11bd7c9267f71fcc2e9c575c9dcdeebd5fe64
Timestamp: 1718357712 Timestamp [UCT]: 2024-06-14 09:35:12 Age [y:d:h:m:s]: 00:349:06:06:35
Block: 1043950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249623 RingCT/type: yes/0
Extra: 01c82281ccf72439c295d37138e4a11bd7c9267f71fcc2e9c575c9dcdeebd5fe6402110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e251004cc71dfab13f355ac3637e653b9d29bd37d8321cf8f359b888299a3e2 0.600000000000 1513119 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": 1043960, "vin": [ { "gen": { "height": 1043950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e251004cc71dfab13f355ac3637e653b9d29bd37d8321cf8f359b888299a3e2" } } ], "extra": [ 1, 200, 34, 129, 204, 247, 36, 57, 194, 149, 211, 113, 56, 228, 161, 27, 215, 201, 38, 127, 113, 252, 194, 233, 197, 117, 201, 220, 222, 235, 213, 254, 100, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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