Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4db64fd3325804567bfca4022f4175aaa062e6ce7e73c275bf378b26be2170b

Tx prefix hash: 90c24e37149d0f26be754f7c048f94f9286befa2f4bdd9080b6f2729b1c869a6
Tx public key: bdbed353f6ce527abb1fe71d7070d4f8d547420de0c8b2e40aa2bdc36032feb5
Timestamp: 1733622426 Timestamp [UCT]: 2024-12-08 01:47:06 Age [y:d:h:m:s]: 00:142:17:28:08
Block: 1170392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101823 RingCT/type: yes/0
Extra: 01bdbed353f6ce527abb1fe71d7070d4f8d547420de0c8b2e40aa2bdc36032feb5021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fff1a431e5f9d9584c50175eb46a04925180216edbc821b7c48e9488af98f7f9 0.600000000000 1656123 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": 1170402, "vin": [ { "gen": { "height": 1170392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fff1a431e5f9d9584c50175eb46a04925180216edbc821b7c48e9488af98f7f9" } } ], "extra": [ 1, 189, 190, 211, 83, 246, 206, 82, 122, 187, 31, 231, 29, 112, 112, 212, 248, 213, 71, 66, 13, 224, 200, 178, 228, 10, 162, 189, 195, 96, 50, 254, 181, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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