Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37413b85acf21fedf2f7873a7bfeb4a0b9984069a2cc5de9060f84a0367de33c

Tx prefix hash: 32d73d6cf4dfdd4c3b0069c6ed8e846cf79ccad2e4aa782cadcb302c6ab1223f
Tx public key: 90844dcaaa6dd2fa74cffa1cac5e2b342b788860f81d5010def111ac0917d692
Timestamp: 1709421244 Timestamp [UCT]: 2024-03-02 23:14:04 Age [y:d:h:m:s]: 01:071:13:11:39
Block: 969850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312169 RingCT/type: yes/0
Extra: 0190844dcaaa6dd2fa74cffa1cac5e2b342b788860f81d5010def111ac0917d69202110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3ab573bcee4c0a391c6b659b43fabb97c3a1a673c3cec5272e2dac3b6db5a51 0.600000000000 1429699 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": 969860, "vin": [ { "gen": { "height": 969850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3ab573bcee4c0a391c6b659b43fabb97c3a1a673c3cec5272e2dac3b6db5a51" } } ], "extra": [ 1, 144, 132, 77, 202, 170, 109, 210, 250, 116, 207, 250, 28, 172, 94, 43, 52, 43, 120, 136, 96, 248, 29, 80, 16, 222, 241, 17, 172, 9, 23, 214, 146, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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