Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b32a498a8ac12700cfac974d691fe4e186e84da4cbb484acb07ce128d85a358a

Tx prefix hash: e5ac372435f68122694fbbf569e26b832956039bf13c2b5e2247ccc72152df81
Tx public key: 2dd733bfee2c9ac71f11a16b8889b79ed337e1e8e95bb80d5417f8f42a058569
Timestamp: 1699661327 Timestamp [UCT]: 2023-11-11 00:08:47 Age [y:d:h:m:s]: 01:139:19:37:42
Block: 888950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361101 RingCT/type: yes/0
Extra: 012dd733bfee2c9ac71f11a16b8889b79ed337e1e8e95bb80d5417f8f42a05856902110000000433af99f4000000000000000000

1 output(s) for total of 0.695888451000 dcy

stealth address amount amount idx
00: caad8a38228d8ee2f8d512ab2a05e908abbb75c6f517da81c01fd80b900a1e43 0.695888451000 1344919 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": 888960, "vin": [ { "gen": { "height": 888950 } } ], "vout": [ { "amount": 695888451, "target": { "key": "caad8a38228d8ee2f8d512ab2a05e908abbb75c6f517da81c01fd80b900a1e43" } } ], "extra": [ 1, 45, 215, 51, 191, 238, 44, 154, 199, 31, 17, 161, 107, 136, 137, 183, 158, 211, 55, 225, 232, 233, 91, 184, 13, 84, 23, 248, 244, 42, 5, 133, 105, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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