Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28ea0481a3597a012966a8e0ca656caa298a311d2833ee771ca748ef461ccf69

Tx prefix hash: c4432300e83d76c92804d434c87a5a972ef0e0d8a4414928b26355f52638fcbe
Tx public key: 4121b9c7c3e9de391d3876faa919736d623f0f73a6a18f9dfba49d41d4572364
Timestamp: 1735275245 Timestamp [UCT]: 2024-12-27 04:54:05 Age [y:d:h:m:s]: 00:094:11:48:15
Block: 1184075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67303 RingCT/type: yes/0
Extra: 014121b9c7c3e9de391d3876faa919736d623f0f73a6a18f9dfba49d41d457236402110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80b862e768943ce64d43b4c87be6ffaebadb6dbc5120708eb00af4a9644c03a1 0.600000000000 1670528 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": 1184085, "vin": [ { "gen": { "height": 1184075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80b862e768943ce64d43b4c87be6ffaebadb6dbc5120708eb00af4a9644c03a1" } } ], "extra": [ 1, 65, 33, 185, 199, 195, 233, 222, 57, 29, 56, 118, 250, 169, 25, 115, 109, 98, 63, 15, 115, 166, 161, 143, 157, 251, 164, 157, 65, 212, 87, 35, 100, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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