Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91ebe783d1b42ae2abd6ee55982da4b46a12a925aad1b0f54d40f4d06b41ad16

Tx prefix hash: 1913f693d6a7c8043a6f909b4e16733150b80b45dc77ebda757943e391827c78
Tx public key: ffd4d0c00de01c6785c132734b3ab8c4195610f2f9847ce270e053ac2ba9fdbf
Timestamp: 1711602888 Timestamp [UCT]: 2024-03-28 05:14:48 Age [y:d:h:m:s]: 01:020:18:33:31
Block: 987960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275784 RingCT/type: yes/0
Extra: 01ffd4d0c00de01c6785c132734b3ab8c4195610f2f9847ce270e053ac2ba9fdbf02110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9c5f9275a8361acff34a4312fd3a6bf3aca686fd3a1334c797e9bcb63b69fdf 0.600000000000 1448221 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": 987970, "vin": [ { "gen": { "height": 987960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9c5f9275a8361acff34a4312fd3a6bf3aca686fd3a1334c797e9bcb63b69fdf" } } ], "extra": [ 1, 255, 212, 208, 192, 13, 224, 28, 103, 133, 193, 50, 115, 75, 58, 184, 196, 25, 86, 16, 242, 249, 132, 124, 226, 112, 224, 83, 172, 43, 169, 253, 191, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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