Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87e9cfff5dab6d1fbe7f8131011d41f198a130e725a74309a3836db5033c6bb7

Tx prefix hash: 4a8db85cdaaa5cd3fce8cf44d2c9c1dcdfc5dd9d2df019d21ef19693151a3b79
Tx public key: f53c11e1d5c02c82a6908a4f3fa2ec0ab2924b4af818a1489c2a4b1cad9bd9ca
Timestamp: 1742081687 Timestamp [UCT]: 2025-03-15 23:34:47 Age [y:d:h:m:s]: 00:250:15:05:18
Block: 1240180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176832 RingCT/type: yes/0
Extra: 01f53c11e1d5c02c82a6908a4f3fa2ec0ab2924b4af818a1489c2a4b1cad9bd9ca02110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 479d4dfda886eba8e874da2a9c2370dfed15407ad9e3cc3725fdd5e0fe17a3ee 0.600000000000 1727145 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": 1240190, "vin": [ { "gen": { "height": 1240180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "479d4dfda886eba8e874da2a9c2370dfed15407ad9e3cc3725fdd5e0fe17a3ee" } } ], "extra": [ 1, 245, 60, 17, 225, 213, 192, 44, 130, 166, 144, 138, 79, 63, 162, 236, 10, 178, 146, 75, 74, 248, 24, 161, 72, 156, 42, 75, 28, 173, 155, 217, 202, 2, 17, 0, 0, 0, 15, 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