Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e77cd15adc8f490017e0cc970a3fe88054b1a9c2ff9d0ed6aa6ded920a5120

Tx prefix hash: 184a8aa09082026662c96cde04f22f93263ff10aa71d221179533d41cb8e9b55
Tx public key: 1dcf4e6bd75928b360ad2a87229ea251dcab3fd39263c3825b72111165da22d2
Timestamp: 1727330333 Timestamp [UCT]: 2024-09-26 05:58:53 Age [y:d:h:m:s]: 00:232:08:07:20
Block: 1118325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165893 RingCT/type: yes/0
Extra: 011dcf4e6bd75928b360ad2a87229ea251dcab3fd39263c3825b72111165da22d2021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46f8c5e7eb0ec01b5c885f7fac172e19eaa99b299d9031d9f41ca82588183bb9 0.600000000000 1599480 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": 1118335, "vin": [ { "gen": { "height": 1118325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46f8c5e7eb0ec01b5c885f7fac172e19eaa99b299d9031d9f41ca82588183bb9" } } ], "extra": [ 1, 29, 207, 78, 107, 215, 89, 40, 179, 96, 173, 42, 135, 34, 158, 162, 81, 220, 171, 63, 211, 146, 99, 195, 130, 91, 114, 17, 17, 101, 218, 34, 210, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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