Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b49d0234700a98560082ff2f60a67a42733e33621dc02b38c52e3236e8b63fee

Tx prefix hash: c3697621b91746cd47dc26e659470c51cf1f991c4cc753b6097087b5c28bf1fe
Tx public key: f3c251f21d719ad863953ca807fe30d9750af10b1105e17df75120b5a64ae20f
Timestamp: 1717119645 Timestamp [UCT]: 2024-05-31 01:40:45 Age [y:d:h:m:s]: 00:300:22:26:25
Block: 1033681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215055 RingCT/type: yes/0
Extra: 01f3c251f21d719ad863953ca807fe30d9750af10b1105e17df75120b5a64ae20f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8c7e34cb608d73ee60c14ecb2126c47d8ad119c9e321d8c9daa33f0b870e675 0.600000000000 1502152 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": 1033691, "vin": [ { "gen": { "height": 1033681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8c7e34cb608d73ee60c14ecb2126c47d8ad119c9e321d8c9daa33f0b870e675" } } ], "extra": [ 1, 243, 194, 81, 242, 29, 113, 154, 216, 99, 149, 60, 168, 7, 254, 48, 217, 117, 10, 241, 11, 17, 5, 225, 125, 247, 81, 32, 181, 166, 74, 226, 15, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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