Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4403d71cbcfb108bf9aa42d4a66e6ad0e1bbc1fc97fa481b7d66b83262677ba1

Tx prefix hash: f222410ea7d3d7bacf701d5a4640ee8952120e986873014bdc6ba2b9fc2d2165
Tx public key: feca5b0838fffc131e512bbf84ee5ab6c0993f59895b6e2595e4d0976d16b90c
Timestamp: 1689920038 Timestamp [UCT]: 2023-07-21 06:13:58 Age [y:d:h:m:s]: 01:313:21:28:10
Block: 808440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485488 RingCT/type: yes/0
Extra: 01feca5b0838fffc131e512bbf84ee5ab6c0993f59895b6e2595e4d0976d16b90c021100000006e6d27f9c000000000000000000

1 output(s) for total of 1.286183098000 dcy

stealth address amount amount idx
00: 2bbd3dd4d1d86f6e0c1ea032e6411b1ac0e6a7ffb51f6279a14e3759c89b7403 1.286183098000 1260015 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": 808450, "vin": [ { "gen": { "height": 808440 } } ], "vout": [ { "amount": 1286183098, "target": { "key": "2bbd3dd4d1d86f6e0c1ea032e6411b1ac0e6a7ffb51f6279a14e3759c89b7403" } } ], "extra": [ 1, 254, 202, 91, 8, 56, 255, 252, 19, 30, 81, 43, 191, 132, 238, 90, 182, 192, 153, 63, 89, 137, 91, 110, 37, 149, 228, 208, 151, 109, 22, 185, 12, 2, 17, 0, 0, 0, 6, 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