Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd13c16aa19b58c72396e4dc3d198468c373fbd74155d73a0a44721ca5049577

Tx prefix hash: 7e2677a92db2e1ee3c564b748aa979429aacf87ac63d340b5348fa9a1ac2527e
Tx public key: cb8123b5a3064941593e45dd7f6fb7f8e31246dbdfc642a96d3059e20fe545fc
Timestamp: 1706557572 Timestamp [UCT]: 2024-01-29 19:46:12 Age [y:d:h:m:s]: 00:290:06:19:28
Block: 946090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207833 RingCT/type: yes/0
Extra: 01cb8123b5a3064941593e45dd7f6fb7f8e31246dbdfc642a96d3059e20fe545fc0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f45011ca08ec35dc895b5d376baca55a993cff76b73700e187e969f31bf748d 0.600000000000 1404420 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": 946100, "vin": [ { "gen": { "height": 946090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f45011ca08ec35dc895b5d376baca55a993cff76b73700e187e969f31bf748d" } } ], "extra": [ 1, 203, 129, 35, 181, 163, 6, 73, 65, 89, 62, 69, 221, 127, 111, 183, 248, 227, 18, 70, 219, 223, 198, 66, 169, 109, 48, 89, 226, 15, 229, 69, 252, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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