Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e37b87e90c19f2f735782ee21d0d62724b67c57fa65c609241e402412171617c

Tx prefix hash: 01953616b0b6d625264ae5866ad8fceb66f004e744d8877361e39ca23195cd64
Tx public key: b0a67ce5ea5c70f65bf16f3fee0eb5edd177281ed5f10a5bc896f2481d50c122
Timestamp: 1729046952 Timestamp [UCT]: 2024-10-16 02:49:12 Age [y:d:h:m:s]: 00:197:12:39:31
Block: 1132579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140951 RingCT/type: yes/0
Extra: 01b0a67ce5ea5c70f65bf16f3fee0eb5edd177281ed5f10a5bc896f2481d50c122021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c61d315b3f9b4d28f4bea914fcf5d08ba0c244a0c483757821d54c51b29360bc 0.600000000000 1615528 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": 1132589, "vin": [ { "gen": { "height": 1132579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c61d315b3f9b4d28f4bea914fcf5d08ba0c244a0c483757821d54c51b29360bc" } } ], "extra": [ 1, 176, 166, 124, 229, 234, 92, 112, 246, 91, 241, 111, 63, 238, 14, 181, 237, 209, 119, 40, 30, 213, 241, 10, 91, 200, 150, 242, 72, 29, 80, 193, 34, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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