Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbc5b30cb463f96ecbf50d45179169dc3ff8ce2af96b412f1cdb447b5aed07c8

Tx prefix hash: f3b1c287fde4026929590a5ae79e4fe0445c184caeff1c51fb0389dd165ade6c
Tx public key: c6531005b6e5bf66f1d0d31b531293990f2b7e8df34b186286de9995f8a0bbf0
Timestamp: 1628728771 Timestamp [UCT]: 2021-08-12 00:39:31 Age [y:d:h:m:s]: 03:286:20:03:42
Block: 312112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 978028 RingCT/type: yes/0
Extra: 01c6531005b6e5bf66f1d0d31b531293990f2b7e8df34b186286de9995f8a0bbf002110000000a17696b73000000000000000000

1 output(s) for total of 56.735038596000 dcy

stealth address amount amount idx
00: 0403e09a95c839591a354e2991d39d7d54e90e15a9fc9f3eb743b1cc7b09e8f1 56.735038596000 649449 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": 312122, "vin": [ { "gen": { "height": 312112 } } ], "vout": [ { "amount": 56735038596, "target": { "key": "0403e09a95c839591a354e2991d39d7d54e90e15a9fc9f3eb743b1cc7b09e8f1" } } ], "extra": [ 1, 198, 83, 16, 5, 182, 229, 191, 102, 241, 208, 211, 27, 83, 18, 147, 153, 15, 43, 126, 141, 243, 75, 24, 98, 134, 222, 153, 149, 248, 160, 187, 240, 2, 17, 0, 0, 0, 10, 23, 105, 107, 115, 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