Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f66bac3cde226705323fe41eeef8fddcae539253893a0bf9d71dff8607f4f69

Tx prefix hash: 49a34550aec7dc856a4aa35317956bad22f1e8219444be4bc2c9aa19fdc0a0c3
Tx public key: ab64c20e952ebcef4438972e1e59587b11ac4f79e48dcae9c7c7f6f7e6faf178
Timestamp: 1716462317 Timestamp [UCT]: 2024-05-23 11:05:17 Age [y:d:h:m:s]: 00:309:22:10:51
Block: 1028233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221504 RingCT/type: yes/0
Extra: 01ab64c20e952ebcef4438972e1e59587b11ac4f79e48dcae9c7c7f6f7e6faf17802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff1f0484479beddf26b7c038740bd91cf88b6ce13705322095b56fded2cdbe1a 0.600000000000 1496194 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": 1028243, "vin": [ { "gen": { "height": 1028233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff1f0484479beddf26b7c038740bd91cf88b6ce13705322095b56fded2cdbe1a" } } ], "extra": [ 1, 171, 100, 194, 14, 149, 46, 188, 239, 68, 56, 151, 46, 30, 89, 88, 123, 17, 172, 79, 121, 228, 141, 202, 233, 199, 199, 246, 247, 230, 250, 241, 120, 2, 17, 0, 0, 0, 2, 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