Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6aae2c2636330baebf44fc25454b4cb36c4e2513a74157c62e7c3bfae0e89dc

Tx prefix hash: b6ea78d46629ff86d7df868196344cb249e94c6f19a80a46c41f98c7201235af
Tx public key: 45743af4c33f28224f35bad490d3b307f0d6e26c268c173be0d4f73ca57cafcf
Timestamp: 1636938469 Timestamp [UCT]: 2021-11-15 01:07:49 Age [y:d:h:m:s]: 03:120:14:56:31
Block: 374486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 864747 RingCT/type: yes/0
Extra: 0145743af4c33f28224f35bad490d3b307f0d6e26c268c173be0d4f73ca57cafcf021100000023e9564d6f000000000000000000

1 output(s) for total of 35.251111332000 dcy

stealth address amount amount idx
00: 6f20d0b26c99a8df2a7a738a6c02f4844cb77b4099cb94de85933ca446c3380d 35.251111332000 757996 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": 374496, "vin": [ { "gen": { "height": 374486 } } ], "vout": [ { "amount": 35251111332, "target": { "key": "6f20d0b26c99a8df2a7a738a6c02f4844cb77b4099cb94de85933ca446c3380d" } } ], "extra": [ 1, 69, 116, 58, 244, 195, 63, 40, 34, 79, 53, 186, 212, 144, 211, 179, 7, 240, 214, 226, 108, 38, 140, 23, 59, 224, 212, 247, 60, 165, 124, 175, 207, 2, 17, 0, 0, 0, 35, 233, 86, 77, 111, 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