Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00d52f1a43f8e9b3bc05a41ffbd4589be4568aad52581d16d134e4f83d04058c

Tx prefix hash: bbca765d2732f67e1e57cc263d234f4374877c0ae2e471383a4f317e72a9401c
Tx public key: 355bc13738deae985d5e83433053bd28313eaa13a4acef5b8acaa26c06a828d9
Timestamp: 1643247634 Timestamp [UCT]: 2022-01-27 01:40:34 Age [y:d:h:m:s]: 02:363:06:36:25
Block: 426049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 778109 RingCT/type: yes/0
Extra: 01355bc13738deae985d5e83433053bd28313eaa13a4acef5b8acaa26c06a828d9021100000002e778ec4c000000000000000000

1 output(s) for total of 23.786093161000 dcy

stealth address amount amount idx
00: 0a6745735e2a2fd43899504bacbd909cabbdcc1a7eeed050aa8f663551fa7b3f 23.786093161000 834824 of 0

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": 426059, "vin": [ { "gen": { "height": 426049 } } ], "vout": [ { "amount": 23786093161, "target": { "key": "0a6745735e2a2fd43899504bacbd909cabbdcc1a7eeed050aa8f663551fa7b3f" } } ], "extra": [ 1, 53, 91, 193, 55, 56, 222, 174, 152, 93, 94, 131, 67, 48, 83, 189, 40, 49, 62, 170, 19, 164, 172, 239, 91, 138, 202, 162, 108, 6, 168, 40, 217, 2, 17, 0, 0, 0, 2, 231, 120, 236, 76, 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