Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20f92cf76477bb90ce6fa4c45865e88c6d04c46bf89ac61a3a4c49eaf279d754

Tx prefix hash: 731fa270d275e62fbe35bff35e8ec5df201162d7e3c2a3a7a3cb38f419a5ad98
Tx public key: 714e98c7785f7401ba33ff085679cff25f5b0b1fcfd541912dadf2f394a810fe
Timestamp: 1702835981 Timestamp [UCT]: 2023-12-17 17:59:41 Age [y:d:h:m:s]: 01:033:17:41:59
Block: 915260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285423 RingCT/type: yes/0
Extra: 01714e98c7785f7401ba33ff085679cff25f5b0b1fcfd541912dadf2f394a810fe021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cab59a7e131f6ca9e86c9893a0813e085f192a1fcd0e37cd5d48c557e5d1617a 0.600000000000 1372650 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": 915270, "vin": [ { "gen": { "height": 915260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cab59a7e131f6ca9e86c9893a0813e085f192a1fcd0e37cd5d48c557e5d1617a" } } ], "extra": [ 1, 113, 78, 152, 199, 120, 95, 116, 1, 186, 51, 255, 8, 86, 121, 207, 242, 95, 91, 11, 31, 207, 213, 65, 145, 45, 173, 242, 243, 148, 168, 16, 254, 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