Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27407ab04664431e5d3f293fe962c526407f3ca201ae5100cd5cd1dbf93fc844

Tx prefix hash: d8dea9ed64b9ce3529acd1e99d3c5f1e4d06734382491760a0a887cec60d4ab6
Tx public key: 7d5956c40be5f32bd2edc1c9b0eb543a81194c19fcf20bc4c5998b6e9200bed6
Timestamp: 1734520625 Timestamp [UCT]: 2024-12-18 11:17:05 Age [y:d:h:m:s]: 00:097:00:22:00
Block: 1177856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69086 RingCT/type: yes/0
Extra: 017d5956c40be5f32bd2edc1c9b0eb543a81194c19fcf20bc4c5998b6e9200bed60211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600100000000 dcy

stealth address amount amount idx
00: b77debc0648806c7867a09aba4bdfd164b1d88418200c89b06dced5626d81bfc 0.600100000000 1664233 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": 1177866, "vin": [ { "gen": { "height": 1177856 } } ], "vout": [ { "amount": 600100000, "target": { "key": "b77debc0648806c7867a09aba4bdfd164b1d88418200c89b06dced5626d81bfc" } } ], "extra": [ 1, 125, 89, 86, 196, 11, 229, 243, 43, 210, 237, 193, 201, 176, 235, 84, 58, 129, 25, 76, 25, 252, 242, 11, 196, 197, 153, 139, 110, 146, 0, 190, 214, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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