Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab83b409c813a71d43d13933c588e4a8d903b6406c924ccb4f323bb9cd00c4ee

Tx prefix hash: e4108b2c0c4d133f488d05fca23c2e7321fff0d9b06625803f803d9f550a78a5
Tx public key: 78069d233898cee18c8b50e3d5bafd078fe5df463565a521fadd2296f50e4fbd
Timestamp: 1673303164 Timestamp [UCT]: 2023-01-09 22:26:04 Age [y:d:h:m:s]: 02:156:06:53:40
Block: 671273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 633347 RingCT/type: yes/0
Extra: 0178069d233898cee18c8b50e3d5bafd078fe5df463565a521fadd2296f50e4fbd021100000005b3e1cbca000000000000000000

1 output(s) for total of 3.662636742000 dcy

stealth address amount amount idx
00: b9b52bccb3e2b3095e9fa94f82a7f6e68018a5217c24cb3bfc1a721862282aa3 3.662636742000 1112732 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": 671283, "vin": [ { "gen": { "height": 671273 } } ], "vout": [ { "amount": 3662636742, "target": { "key": "b9b52bccb3e2b3095e9fa94f82a7f6e68018a5217c24cb3bfc1a721862282aa3" } } ], "extra": [ 1, 120, 6, 157, 35, 56, 152, 206, 225, 140, 139, 80, 227, 213, 186, 253, 7, 143, 229, 223, 70, 53, 101, 165, 33, 250, 221, 34, 150, 245, 14, 79, 189, 2, 17, 0, 0, 0, 5, 179, 225, 203, 202, 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