Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff22b921e104ea546748be858bcd092dbe3603e76a4c717417a1132329802aed

Tx prefix hash: 2c5a5e5314a7a4dbf734ae978f2eacf71b9a9f51e78fcc78548868edc0056802
Tx public key: 4f8d4f50a95724aafd9b8b9f3ed2f9a985ffc23327f56b314529a7db8a792626
Timestamp: 1658747246 Timestamp [UCT]: 2022-07-25 11:07:26 Age [y:d:h:m:s]: 02:281:01:07:22
Block: 551353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 722069 RingCT/type: yes/0
Extra: 014f8d4f50a95724aafd9b8b9f3ed2f9a985ffc23327f56b314529a7db8a792626021100000004e6d27f9c000000000000000000

1 output(s) for total of 9.144053614000 dcy

stealth address amount amount idx
00: a1b22b4c0c8137eaa0a3b192a779c342349213e345613d059185d9873e487ef3 9.144053614000 982939 of 0

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": 551363, "vin": [ { "gen": { "height": 551353 } } ], "vout": [ { "amount": 9144053614, "target": { "key": "a1b22b4c0c8137eaa0a3b192a779c342349213e345613d059185d9873e487ef3" } } ], "extra": [ 1, 79, 141, 79, 80, 169, 87, 36, 170, 253, 155, 139, 159, 62, 210, 249, 169, 133, 255, 194, 51, 39, 245, 107, 49, 69, 41, 167, 219, 138, 121, 38, 38, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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