Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 252c45b27fb816e742ae096a90bb98a29ad71d0fe13a67b611dfb50a272b2de5

Tx prefix hash: 82c2f1236461617e05a4ba3f440ba3745546ee4aae2366b5f2904afed69c6611
Tx public key: bc096c51c5b2b6729c70361cead449d77d891bd5706a1081b40aef7f240dd922
Timestamp: 1720610878 Timestamp [UCT]: 2024-07-10 11:27:58 Age [y:d:h:m:s]: 00:290:13:40:03
Block: 1062629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207613 RingCT/type: yes/0
Extra: 01bc096c51c5b2b6729c70361cead449d77d891bd5706a1081b40aef7f240dd922021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cafbf49d649ae76bc4f3dc8e1853582572458d1babbcad1e3a4c90196b30ffc5 0.600000000000 1533134 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": 1062639, "vin": [ { "gen": { "height": 1062629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cafbf49d649ae76bc4f3dc8e1853582572458d1babbcad1e3a4c90196b30ffc5" } } ], "extra": [ 1, 188, 9, 108, 81, 197, 178, 182, 114, 156, 112, 54, 28, 234, 212, 73, 215, 125, 137, 27, 213, 112, 106, 16, 129, 180, 10, 239, 127, 36, 13, 217, 34, 2, 17, 0, 0, 0, 3, 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