Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f38033929dd0f2486766c149216d92d304bc4c55934a818b81d4eed0ace67a16

Tx prefix hash: 6287a1ed6320dc0986d7b1adb7d838326b4517e0d1292a840410f4636d3c5eab
Tx public key: 69f2b70eeefbcb4c2000f35593dbccf131d5d953a2e9e27dbf3cc1ef406570bc
Timestamp: 1726888041 Timestamp [UCT]: 2024-09-21 03:07:21 Age [y:d:h:m:s]: 01:049:07:30:20
Block: 1114666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293645 RingCT/type: yes/0
Extra: 0169f2b70eeefbcb4c2000f35593dbccf131d5d953a2e9e27dbf3cc1ef406570bc021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e53568baff75b7e118cd145630780d1ab3e34f5e466dd6d6d58cc1e0ab7c9a10 0.600000000000 1594523 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": 1114676, "vin": [ { "gen": { "height": 1114666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e53568baff75b7e118cd145630780d1ab3e34f5e466dd6d6d58cc1e0ab7c9a10" } } ], "extra": [ 1, 105, 242, 183, 14, 238, 251, 203, 76, 32, 0, 243, 85, 147, 219, 204, 241, 49, 213, 217, 83, 162, 233, 226, 125, 191, 60, 193, 239, 64, 101, 112, 188, 2, 17, 0, 0, 0, 3, 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