Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dad472c7402609634c7f666fa44952ef73ae30d3f1109b9923130a09cafa3be

Tx prefix hash: 25e65871bd33eba91dba79db0243c3f8a040a6cddd796251ca299e11e580f8a9
Tx public key: cb496614eb9a07a9dbf360eabd796a58093e4c4ab6dc256e7ef3a7fc4f1f05a7
Timestamp: 1740845685 Timestamp [UCT]: 2025-03-01 16:14:45 Age [y:d:h:m:s]: 00:264:06:13:14
Block: 1229914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186616 RingCT/type: yes/0
Extra: 01cb496614eb9a07a9dbf360eabd796a58093e4c4ab6dc256e7ef3a7fc4f1f05a702110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4dc77a65550cec710df9126482f3090ee14de61aa527c6bb0c221bcb03dde17 0.600000000000 1716805 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": 1229924, "vin": [ { "gen": { "height": 1229914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4dc77a65550cec710df9126482f3090ee14de61aa527c6bb0c221bcb03dde17" } } ], "extra": [ 1, 203, 73, 102, 20, 235, 154, 7, 169, 219, 243, 96, 234, 189, 121, 106, 88, 9, 62, 76, 74, 182, 220, 37, 110, 126, 243, 167, 252, 79, 31, 5, 167, 2, 17, 0, 0, 0, 15, 0, 127, 151, 138, 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