Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5a4cc6d282b4c4ad096888b38e9e9149ae7c23f76d354f54b56708df6b2e652

Tx prefix hash: c793ac665f534fef9bfbb0167f12f6ebd4654af9c8024c80f4bb851f8931bd6e
Tx public key: baa473b25b2c06c484e1899218c5a9f969ae714db0f25781e5131f4994eeefc8
Timestamp: 1732629769 Timestamp [UCT]: 2024-11-26 14:02:49 Age [y:d:h:m:s]: 00:137:11:06:59
Block: 1162164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98053 RingCT/type: yes/0
Extra: 01baa473b25b2c06c484e1899218c5a9f969ae714db0f25781e5131f4994eeefc80211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a9ac83689b8f2045fb97a5c48c189523e382a5d3e8e5f39d28cc352f3aef313 0.600000000000 1647819 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": 1162174, "vin": [ { "gen": { "height": 1162164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a9ac83689b8f2045fb97a5c48c189523e382a5d3e8e5f39d28cc352f3aef313" } } ], "extra": [ 1, 186, 164, 115, 178, 91, 44, 6, 196, 132, 225, 137, 146, 24, 197, 169, 249, 105, 174, 113, 77, 176, 242, 87, 129, 229, 19, 31, 73, 148, 238, 239, 200, 2, 17, 0, 0, 0, 5, 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