Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f78c7be32ceda90b0057a3ca0353662a72421d23f98dfd782e3a9640d74bac10

Tx prefix hash: 601de08a4e3a7ceced9767f91c422638f30934f7658e6807d6de5f4130a1d98c
Tx public key: e85836f00d754d1db2e1c5d20d8c35a6b759b6628112c8f22adc13bbb0b03b8c
Timestamp: 1735548673 Timestamp [UCT]: 2024-12-30 08:51:13 Age [y:d:h:m:s]: 00:106:07:31:56
Block: 1186329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75776 RingCT/type: yes/0
Extra: 01e85836f00d754d1db2e1c5d20d8c35a6b759b6628112c8f22adc13bbb0b03b8c0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c336584b134c227b9e97bce10965c98ae8f52893adb18748966cb9b7b5309c6c 0.600000000000 1672808 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": 1186339, "vin": [ { "gen": { "height": 1186329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c336584b134c227b9e97bce10965c98ae8f52893adb18748966cb9b7b5309c6c" } } ], "extra": [ 1, 232, 88, 54, 240, 13, 117, 77, 29, 178, 225, 197, 210, 13, 140, 53, 166, 183, 89, 182, 98, 129, 18, 200, 242, 42, 220, 19, 187, 176, 176, 59, 140, 2, 17, 0, 0, 0, 6, 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