Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc6bd62521d6f1c3d5bd48174bb9c4e752dd38a8922ad20d85b7763269b4829a

Tx prefix hash: b9fc156f92d2ac25de6f91b3db898aefd6552aed55cd8c2fa03e27b89d58deeb
Tx public key: 2da9b17ab3dfd13b175784fe9029441736e9af1054a171cca9f67da4a8eb655c
Timestamp: 1576424499 Timestamp [UCT]: 2019-12-15 15:41:39 Age [y:d:h:m:s]: 05:149:17:39:25
Block: 27386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1253824 RingCT/type: yes/0
Extra: 012da9b17ab3dfd13b175784fe9029441736e9af1054a171cca9f67da4a8eb655c021100000040ad433a0b000000000000000000

1 output(s) for total of 498.092848139000 dcy

stealth address amount amount idx
00: ebee8978cb683badb10b27d041c42a0647f9b12f3fb818a7728c7ed6e2349495 498.092848139000 45384 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": 27396, "vin": [ { "gen": { "height": 27386 } } ], "vout": [ { "amount": 498092848139, "target": { "key": "ebee8978cb683badb10b27d041c42a0647f9b12f3fb818a7728c7ed6e2349495" } } ], "extra": [ 1, 45, 169, 177, 122, 179, 223, 209, 59, 23, 87, 132, 254, 144, 41, 68, 23, 54, 233, 175, 16, 84, 161, 113, 204, 169, 246, 125, 164, 168, 235, 101, 92, 2, 17, 0, 0, 0, 64, 173, 67, 58, 11, 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