Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bef944908ad378fc2ca1588c1476c787d2719887c2c648323a8a0ce4d00e5b8f

Tx prefix hash: dd03fcdf813e44a847cdfbe9386ee1bd2515d3b6b226243aabc1d945a7a3cabf
Tx public key: b206b90169ebf2132578d8879e64cf68bd5ea0a7b6276356f39af53d4e630870
Timestamp: 1648015998 Timestamp [UCT]: 2022-03-23 06:13:18 Age [y:d:h:m:s]: 02:321:21:58:41
Block: 464484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 749353 RingCT/type: yes/0
Extra: 01b206b90169ebf2132578d8879e64cf68bd5ea0a7b6276356f39af53d4e630870021100000019d3fcec30000000000000000000

1 output(s) for total of 17.740748903000 dcy

stealth address amount amount idx
00: 1b2d0b1fe5c752cf4c87775bea911e0a8276c1e33ecc894f74599b38007dc47f 17.740748903000 882373 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": 464494, "vin": [ { "gen": { "height": 464484 } } ], "vout": [ { "amount": 17740748903, "target": { "key": "1b2d0b1fe5c752cf4c87775bea911e0a8276c1e33ecc894f74599b38007dc47f" } } ], "extra": [ 1, 178, 6, 185, 1, 105, 235, 242, 19, 37, 120, 216, 135, 158, 100, 207, 104, 189, 94, 160, 167, 182, 39, 99, 86, 243, 154, 245, 61, 78, 99, 8, 112, 2, 17, 0, 0, 0, 25, 211, 252, 236, 48, 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