Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e356e108fff36039ee1c056091d9a94d04f2f8d4145b04a13c2f4b15f31af200

Tx prefix hash: 1224c2745c87335da4976a1adc3b27399e08c1ba907752d72d399ac7c36044b2
Tx public key: beee94a72dc5d8e8653fa651cb3833ef7e24986b89d741a88ae6680e294e6ed6
Timestamp: 1698230651 Timestamp [UCT]: 2023-10-25 10:44:11 Age [y:d:h:m:s]: 01:121:05:20:17
Block: 877295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347589 RingCT/type: yes/0
Extra: 01beee94a72dc5d8e8653fa651cb3833ef7e24986b89d741a88ae6680e294e6ed6021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.760602063000 dcy

stealth address amount amount idx
00: 1a0cf4a0cfe4c470dcc3af9cb03a5f635190da2949d591891837a42df4c16efe 0.760602063000 1332665 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": 877305, "vin": [ { "gen": { "height": 877295 } } ], "vout": [ { "amount": 760602063, "target": { "key": "1a0cf4a0cfe4c470dcc3af9cb03a5f635190da2949d591891837a42df4c16efe" } } ], "extra": [ 1, 190, 238, 148, 167, 45, 197, 216, 232, 101, 63, 166, 81, 203, 56, 51, 239, 126, 36, 152, 107, 137, 215, 65, 168, 138, 230, 104, 14, 41, 78, 110, 214, 2, 17, 0, 0, 0, 5, 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