Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c1e51f065cc4832e05c727af192d6985dbcc27f5f32809da2e131fef5c119a0

Tx prefix hash: a5bf46bd0ae5ee505d4ac1aff04c580d9275784747f084bb45711593b9ea5fb3
Tx public key: 07c944802a75dfd12c4c20d0f40dc0ffafd231df27b88456a0ae4aa05a96b2d1
Timestamp: 1709859645 Timestamp [UCT]: 2024-03-08 01:00:45 Age [y:d:h:m:s]: 01:257:06:09:30
Block: 973496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442578 RingCT/type: yes/0
Extra: 0107c944802a75dfd12c4c20d0f40dc0ffafd231df27b88456a0ae4aa05a96b2d102110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9ff6b5e4275f533618572b17caaf600f34869688bff079766b10c06839df800 0.600000000000 1433431 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": 973506, "vin": [ { "gen": { "height": 973496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9ff6b5e4275f533618572b17caaf600f34869688bff079766b10c06839df800" } } ], "extra": [ 1, 7, 201, 68, 128, 42, 117, 223, 209, 44, 76, 32, 208, 244, 13, 192, 255, 175, 210, 49, 223, 39, 184, 132, 86, 160, 174, 74, 160, 90, 150, 178, 209, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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