Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 710b5c2dae7df75a35ada17b1465fb04a671236484dfedb36b9c45c71ae2ea75

Tx prefix hash: 17478752aedfd243d0680a8b53032ddf5e0ea59a43ef041ee56cb68d486d307e
Tx public key: b1d81585728fa54a16e9b4b78ccb339572845579b69901b9aa80d29b691c1640
Timestamp: 1707072265 Timestamp [UCT]: 2024-02-04 18:44:25 Age [y:d:h:m:s]: 00:345:03:46:37
Block: 950363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247103 RingCT/type: yes/0
Extra: 01b1d81585728fa54a16e9b4b78ccb339572845579b69901b9aa80d29b691c16400211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1451978de3d2e96388ea429e85fb380c10acd178e4d0f618d08e3b9883fb8879 0.600000000000 1408969 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": 950373, "vin": [ { "gen": { "height": 950363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1451978de3d2e96388ea429e85fb380c10acd178e4d0f618d08e3b9883fb8879" } } ], "extra": [ 1, 177, 216, 21, 133, 114, 143, 165, 74, 22, 233, 180, 183, 140, 203, 51, 149, 114, 132, 85, 121, 182, 153, 1, 185, 170, 128, 210, 155, 105, 28, 22, 64, 2, 17, 0, 0, 0, 3, 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