Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c48cf3ba0854b6de1456ecb3521b465dce5f5ff99b2bcb962684f5abe01c9abd

Tx prefix hash: 55b0ac2b6f216482d0e429b7e7bfbd1ef21a35b1c31a797125ea4bb80b9eee99
Tx public key: 97df6b60caf32d39b47e5328d73ea1738ea1106b18bebb1e22e5dfb1c503375c
Timestamp: 1674353320 Timestamp [UCT]: 2023-01-22 02:08:40 Age [y:d:h:m:s]: 02:035:07:33:20
Block: 679989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546857 RingCT/type: yes/0
Extra: 0197df6b60caf32d39b47e5328d73ea1738ea1106b18bebb1e22e5dfb1c503375c0211000000015029cbac000000000000000000

1 output(s) for total of 3.427000034000 dcy

stealth address amount amount idx
00: 6efa115ff75daf58c4994259678a9b1e2cde0d33ea9d9ebaec47300df0a777d8 3.427000034000 1122012 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": 679999, "vin": [ { "gen": { "height": 679989 } } ], "vout": [ { "amount": 3427000034, "target": { "key": "6efa115ff75daf58c4994259678a9b1e2cde0d33ea9d9ebaec47300df0a777d8" } } ], "extra": [ 1, 151, 223, 107, 96, 202, 243, 45, 57, 180, 126, 83, 40, 215, 62, 161, 115, 142, 161, 16, 107, 24, 190, 187, 30, 34, 229, 223, 177, 197, 3, 55, 92, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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