Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c3fbe46cd06e0d6cea413bbfd9d94c46232cb9de305b16d0454735f05249aae

Tx prefix hash: 41fc5895947479c94b5285412aa9ff2dbcd9cba6bdd34bc9c806effa432c2bd0
Tx public key: 389e07c344474b23c6af24e335f31fcba36fb82bdd18903b9e2a32369c325e1c
Timestamp: 1731759637 Timestamp [UCT]: 2024-11-16 12:20:37 Age [y:d:h:m:s]: 00:123:09:52:29
Block: 1154969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88026 RingCT/type: yes/0
Extra: 01389e07c344474b23c6af24e335f31fcba36fb82bdd18903b9e2a32369c325e1c021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b94ea7986f9235e0ef46dfc2d3ff44c8cf64478356657540f145a3d4d42a2577 0.600000000000 1640582 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": 1154979, "vin": [ { "gen": { "height": 1154969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b94ea7986f9235e0ef46dfc2d3ff44c8cf64478356657540f145a3d4d42a2577" } } ], "extra": [ 1, 56, 158, 7, 195, 68, 71, 75, 35, 198, 175, 36, 227, 53, 243, 31, 203, 163, 111, 184, 43, 221, 24, 144, 59, 158, 42, 50, 54, 156, 50, 94, 28, 2, 17, 0, 0, 0, 5, 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