Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b66596685a9412effa22b0881a1b737620824e3f1ca0fbb6eb3be45f76e76bda

Tx prefix hash: 6c6513fdd359e6d48b3f28bcfa4ebbd1f146050b75ce34897831ffdfe8ff0953
Tx public key: 4059e9259776a84968bde2228fcdee4c3233309675c48e2c76d5bf1f0dea2883
Timestamp: 1700428023 Timestamp [UCT]: 2023-11-19 21:07:03 Age [y:d:h:m:s]: 01:062:21:43:46
Block: 895290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306321 RingCT/type: yes/0
Extra: 014059e9259776a84968bde2228fcdee4c3233309675c48e2c76d5bf1f0dea2883021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.663029066000 dcy

stealth address amount amount idx
00: e70e1a631754b35fc0bee226096f56982b52590e9c31b08a5ca22e9c4f42e7cb 0.663029066000 1351519 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": 895300, "vin": [ { "gen": { "height": 895290 } } ], "vout": [ { "amount": 663029066, "target": { "key": "e70e1a631754b35fc0bee226096f56982b52590e9c31b08a5ca22e9c4f42e7cb" } } ], "extra": [ 1, 64, 89, 233, 37, 151, 118, 168, 73, 104, 189, 226, 34, 143, 205, 238, 76, 50, 51, 48, 150, 117, 196, 142, 44, 118, 213, 191, 31, 13, 234, 40, 131, 2, 17, 0, 0, 0, 8, 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