Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba34c39849a5fd9bca87b9a8d3e395bb68f553d921357e655b5096009ae49eef

Tx prefix hash: 313e08d3e8803ec27a50b5e48aa4005223a1d6654ee017a983e26b32c88d3083
Tx public key: 0c31cfd510a28cf0cf421b853b66e2e6f74f0994432f68f76e963654f629593e
Timestamp: 1731244959 Timestamp [UCT]: 2024-11-10 13:22:39 Age [y:d:h:m:s]: 00:013:21:29:38
Block: 1150691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9946 RingCT/type: yes/0
Extra: 010c31cfd510a28cf0cf421b853b66e2e6f74f0994432f68f76e963654f629593e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02127ae355fe0e0dd76b1047ffc4fded679b03c167879311172128a9c4bd5dc6 0.600000000000 1636068 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": 1150701, "vin": [ { "gen": { "height": 1150691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02127ae355fe0e0dd76b1047ffc4fded679b03c167879311172128a9c4bd5dc6" } } ], "extra": [ 1, 12, 49, 207, 213, 16, 162, 140, 240, 207, 66, 27, 133, 59, 102, 226, 230, 247, 79, 9, 148, 67, 47, 104, 247, 110, 150, 54, 84, 246, 41, 89, 62, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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