Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9637e1251c9762e50f0e131fc74281fa6d312b758481d855dafbb8836a9ccc04

Tx prefix hash: 7bfdcd061653b2bd07129d3e794a9925d6ec1e8a11d96e11ca3a6b2783f89d45
Tx public key: 70653918f0e27a251e5b45be1c75c696dcdba90e1afe1ae19ec9eb404ad29f58
Timestamp: 1712665711 Timestamp [UCT]: 2024-04-09 12:28:31 Age [y:d:h:m:s]: 00:260:08:27:20
Block: 996728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186403 RingCT/type: yes/0
Extra: 0170653918f0e27a251e5b45be1c75c696dcdba90e1afe1ae19ec9eb404ad29f580211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 068fc08426b46b3807fce7435ee0c76992e4b6dfc30eb9d067058b0835c422c6 0.600000000000 1457154 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": 996738, "vin": [ { "gen": { "height": 996728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "068fc08426b46b3807fce7435ee0c76992e4b6dfc30eb9d067058b0835c422c6" } } ], "extra": [ 1, 112, 101, 57, 24, 240, 226, 122, 37, 30, 91, 69, 190, 28, 117, 198, 150, 220, 219, 169, 14, 26, 254, 26, 225, 158, 201, 235, 64, 74, 210, 159, 88, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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