Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 577dc8220262218c2e5a738d897da7122201f433dd2c8af9f6340155699d56ca

Tx prefix hash: 9b7c27db7f7e81951a3e92a6a4f60e1e970e2961949d5280c1f9095f523e7f9e
Tx public key: cdc34f9e553af8d808d03af049f113ddc8ba44d6c1b2c37364104f1ec9ad6f1c
Timestamp: 1695607998 Timestamp [UCT]: 2023-09-25 02:13:18 Age [y:d:h:m:s]: 01:196:01:13:35
Block: 855536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401163 RingCT/type: yes/0
Extra: 01cdc34f9e553af8d808d03af049f113ddc8ba44d6c1b2c37364104f1ec9ad6f1c021100000011faf35c9c000000000000000000

1 output(s) for total of 0.897954085000 dcy

stealth address amount amount idx
00: 8d95313f2fd761b4bf24287cfb753bbb42881de4f8d61f7bfa315df07478c7d1 0.897954085000 1309562 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": 855546, "vin": [ { "gen": { "height": 855536 } } ], "vout": [ { "amount": 897954085, "target": { "key": "8d95313f2fd761b4bf24287cfb753bbb42881de4f8d61f7bfa315df07478c7d1" } } ], "extra": [ 1, 205, 195, 79, 158, 85, 58, 248, 216, 8, 208, 58, 240, 73, 241, 19, 221, 200, 186, 68, 214, 193, 178, 195, 115, 100, 16, 79, 30, 201, 173, 111, 28, 2, 17, 0, 0, 0, 17, 250, 243, 92, 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