Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05fe3d1fe3ef0a15187194eaf3b378b8d35d0c6a159a084487f150446321150d

Tx prefix hash: 0ff45b4f8b10a54ccb5d29d0bd7e070b55e490a1d5c434a84d08461c3c7de013
Tx public key: a03ecc5edd97aa129e817af2797bc4447c823a7d8cee3f9e16a76069edaeed2e
Timestamp: 1725529858 Timestamp [UCT]: 2024-09-05 09:50:58 Age [y:d:h:m:s]: 00:211:07:10:38
Block: 1103404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150855 RingCT/type: yes/0
Extra: 01a03ecc5edd97aa129e817af2797bc4447c823a7d8cee3f9e16a76069edaeed2e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 264a9cc6ded2868761e7b59cc8b2cf91f2791e59d71d88617e2aeb46f41d6b11 0.600000000000 1580221 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": 1103414, "vin": [ { "gen": { "height": 1103404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "264a9cc6ded2868761e7b59cc8b2cf91f2791e59d71d88617e2aeb46f41d6b11" } } ], "extra": [ 1, 160, 62, 204, 94, 221, 151, 170, 18, 158, 129, 122, 242, 121, 123, 196, 68, 124, 130, 58, 125, 140, 238, 63, 158, 22, 167, 96, 105, 237, 174, 237, 46, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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