Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d90c087cbfc64b09d8177539fa2253260c3103ba9de29c7f2c79bcc037ef454e

Tx prefix hash: bb093d853702fe1a564f9d8a32326fdc87e80fff0a4ed1b4446e713bd78f78cc
Tx public key: d0758f2ad49544332d66fcef2341fbc926cc8c9718eea63df61721735acb9c8c
Timestamp: 1712480997 Timestamp [UCT]: 2024-04-07 09:09:57 Age [y:d:h:m:s]: 01:239:00:34:19
Block: 995197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429559 RingCT/type: yes/0
Extra: 01d0758f2ad49544332d66fcef2341fbc926cc8c9718eea63df61721735acb9c8c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97d7ea68a27ea2616e5aeddcb90b3641ec8ce4adcfb5536e5d842c724ddef7e8 0.600000000000 1455603 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": 995207, "vin": [ { "gen": { "height": 995197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97d7ea68a27ea2616e5aeddcb90b3641ec8ce4adcfb5536e5d842c724ddef7e8" } } ], "extra": [ 1, 208, 117, 143, 42, 212, 149, 68, 51, 45, 102, 252, 239, 35, 65, 251, 201, 38, 204, 140, 151, 24, 238, 166, 61, 246, 23, 33, 115, 90, 203, 156, 140, 2, 17, 0, 0, 0, 1, 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