Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e89f3012ae62c0e11ee88b2cb9e1557a1a14523ba1e3decc14559d8c4d5861d9

Tx prefix hash: e574ab847075996d3ad1a9e3c223c1a8accc65e86983c680bf7364671d225642
Tx public key: dd70bf7e2aa54549c1a73e11bbd5edc756582cd675becaa7bd1a57ca60cf1baa
Timestamp: 1727278015 Timestamp [UCT]: 2024-09-25 15:26:55 Age [y:d:h:m:s]: 01:056:04:42:16
Block: 1117897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298563 RingCT/type: yes/0
Extra: 01dd70bf7e2aa54549c1a73e11bbd5edc756582cd675becaa7bd1a57ca60cf1baa02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 824379d821a5c9f5c286836f6a3dc19f3eb78f4559ea0bf7555846f3ab838869 0.600000000000 1598896 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": 1117907, "vin": [ { "gen": { "height": 1117897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "824379d821a5c9f5c286836f6a3dc19f3eb78f4559ea0bf7555846f3ab838869" } } ], "extra": [ 1, 221, 112, 191, 126, 42, 165, 69, 73, 193, 167, 62, 17, 187, 213, 237, 199, 86, 88, 44, 214, 117, 190, 202, 167, 189, 26, 87, 202, 96, 207, 27, 170, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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