Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 426ae6c79dad25ed8dfc3189ec1efa74e940b92a16bc9328c8d634ae80e9814c

Tx prefix hash: 72cc6db162ceb4e4f613c41411ebb491f56c1d7e04d316a28f7c5d93302e8dc0
Tx public key: c48e42399aa78000fb99c46384f5f9721a9be9743fcaeeb9f207b1faf83f7daa
Timestamp: 1717547975 Timestamp [UCT]: 2024-06-05 00:39:35 Age [y:d:h:m:s]: 00:284:10:19:30
Block: 1037236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203267 RingCT/type: yes/0
Extra: 01c48e42399aa78000fb99c46384f5f9721a9be9743fcaeeb9f207b1faf83f7daa0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 288e0814568ff345486ea0fd4c4831e913cdcc3faf8a5b0794a7d6e47b449b2b 0.600000000000 1505767 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": 1037246, "vin": [ { "gen": { "height": 1037236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "288e0814568ff345486ea0fd4c4831e913cdcc3faf8a5b0794a7d6e47b449b2b" } } ], "extra": [ 1, 196, 142, 66, 57, 154, 167, 128, 0, 251, 153, 196, 99, 132, 245, 249, 114, 26, 155, 233, 116, 63, 202, 238, 185, 242, 7, 177, 250, 248, 63, 125, 170, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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