Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a16894985a7613d55d4a8a5e206bf64031f23f2093e36c19b646bba6ac81aff6

Tx prefix hash: 3a768fe93aae66475d1f133dcc0222c9bedad858ae3236d098f9b40a621c602e
Tx public key: 7cc570ec1a8b57c4415df8ab4e07edc44c88a4bdccec30ab0660e23d352f6a0a
Timestamp: 1708690678 Timestamp [UCT]: 2024-02-23 12:17:58 Age [y:d:h:m:s]: 01:024:22:51:37
Block: 963795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278867 RingCT/type: yes/0
Extra: 017cc570ec1a8b57c4415df8ab4e07edc44c88a4bdccec30ab0660e23d352f6a0a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f4626b68f919468163d9eccbec11851d5fe9e7e5bbb63054275684dafed470a 0.600000000000 1423522 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": 963805, "vin": [ { "gen": { "height": 963795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f4626b68f919468163d9eccbec11851d5fe9e7e5bbb63054275684dafed470a" } } ], "extra": [ 1, 124, 197, 112, 236, 26, 139, 87, 196, 65, 93, 248, 171, 78, 7, 237, 196, 76, 136, 164, 189, 204, 236, 48, 171, 6, 96, 226, 61, 53, 47, 106, 10, 2, 17, 0, 0, 0, 3, 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