Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38fec70da8b96b553577de2acc5409a1af909b8f9bceb648f55c4361a204530f

Tx prefix hash: 55a45e55a94101f694d917af9d2501216ac5378fb91c20e178be29bea328cb74
Tx public key: e84219da163f04c82cbc60c2bf8d8fa06968c5ca0774179b2f4bb1aec73ca6c3
Timestamp: 1702782903 Timestamp [UCT]: 2023-12-17 03:15:03 Age [y:d:h:m:s]: 01:035:04:28:14
Block: 914817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286451 RingCT/type: yes/0
Extra: 01e84219da163f04c82cbc60c2bf8d8fa06968c5ca0774179b2f4bb1aec73ca6c3021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f5d6fb1600f2432c091d2366645791e575d37ab6d502e5d1f6e0a29603a04ae 0.600000000000 1372169 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": 914827, "vin": [ { "gen": { "height": 914817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f5d6fb1600f2432c091d2366645791e575d37ab6d502e5d1f6e0a29603a04ae" } } ], "extra": [ 1, 232, 66, 25, 218, 22, 63, 4, 200, 44, 188, 96, 194, 191, 141, 143, 160, 105, 104, 197, 202, 7, 116, 23, 155, 47, 75, 177, 174, 199, 60, 166, 195, 2, 17, 0, 0, 0, 1, 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