Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4dfb889bef487f0f7c603c32a2170e8e35144282634511d6f2323ef37970388

Tx prefix hash: c43aedaa7e86184ecba3f30010030e0fc97b378cb1588dfc4bfa577b38aef82a
Tx public key: b37ca683647d1af827e0a92356c690c16f6c40fc8c79bf6bf28dc41b8c2a9f34
Timestamp: 1574102969 Timestamp [UCT]: 2019-11-18 18:49:29 Age [y:d:h:m:s]: 05:176:00:55:21
Block: 12052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1268759 RingCT/type: yes/0
Extra: 01b37ca683647d1af827e0a92356c690c16f6c40fc8c79bf6bf28dc41b8c2a9f34021100000002ccefb800000000000000000000

1 output(s) for total of 559.844749391000 dcy

stealth address amount amount idx
00: 1b351c78fb93af4bbe24d29d4c88d4596fa322f17eb34d4c50d88d0083c9471b 559.844749391000 13139 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": 12062, "vin": [ { "gen": { "height": 12052 } } ], "vout": [ { "amount": 559844749391, "target": { "key": "1b351c78fb93af4bbe24d29d4c88d4596fa322f17eb34d4c50d88d0083c9471b" } } ], "extra": [ 1, 179, 124, 166, 131, 100, 125, 26, 248, 39, 224, 169, 35, 86, 198, 144, 193, 111, 108, 64, 252, 140, 121, 191, 107, 242, 141, 196, 27, 140, 42, 159, 52, 2, 17, 0, 0, 0, 2, 204, 239, 184, 0, 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