Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f01016ac0fc74645bbadb88fec2ff9e01d917cfd4b74e5637a9909eeb669e4aa

Tx prefix hash: 9190b226a981da8f6e41da49487c8d9a5661c8e09611e3209790c10a6c9ba31a
Tx public key: e4cc2368bb39107094c77a00ed4f8f344c0362427c748e886672dcda091b50e8
Timestamp: 1700809104 Timestamp [UCT]: 2023-11-24 06:58:24 Age [y:d:h:m:s]: 02:010:22:44:59
Block: 898446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527617 RingCT/type: yes/0
Extra: 01e4cc2368bb39107094c77a00ed4f8f344c0362427c748e886672dcda091b50e80211000000024b8f5122000000000000000000

1 output(s) for total of 0.647255016000 dcy

stealth address amount amount idx
00: e06c584519f733cf615f52d0a45a6a111f042e31079daef6d4e818073108e2f1 0.647255016000 1354861 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": 898456, "vin": [ { "gen": { "height": 898446 } } ], "vout": [ { "amount": 647255016, "target": { "key": "e06c584519f733cf615f52d0a45a6a111f042e31079daef6d4e818073108e2f1" } } ], "extra": [ 1, 228, 204, 35, 104, 187, 57, 16, 112, 148, 199, 122, 0, 237, 79, 143, 52, 76, 3, 98, 66, 124, 116, 142, 136, 102, 114, 220, 218, 9, 27, 80, 232, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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