Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ed643a359e5144b6036269ddb6c96f587b8af19aad785a1b446c79866ff9c8e

Tx prefix hash: c74436d0f7f23a1552757904001af7c1b4057a5277c68309f2fe1676b72dab2b
Tx public key: aff93c12a7f248d6fee7a62486776e70350fd3aa39e82fbc0bb34615f5ba47a8
Timestamp: 1577855481 Timestamp [UCT]: 2020-01-01 05:11:21 Age [y:d:h:m:s]: 05:307:19:01:19
Block: 36155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1367543 RingCT/type: yes/0
Extra: 01aff93c12a7f248d6fee7a62486776e70350fd3aa39e82fbc0bb34615f5ba47a80211000000924ac5aa02000000000000000000

1 output(s) for total of 465.805196949000 dcy

stealth address amount amount idx
00: acc76c6ebd05359d5fb05161469036d807e4f46f94a757dcb44edb8a7aa3f475 465.805196949000 61158 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": 36165, "vin": [ { "gen": { "height": 36155 } } ], "vout": [ { "amount": 465805196949, "target": { "key": "acc76c6ebd05359d5fb05161469036d807e4f46f94a757dcb44edb8a7aa3f475" } } ], "extra": [ 1, 175, 249, 60, 18, 167, 242, 72, 214, 254, 231, 166, 36, 134, 119, 110, 112, 53, 15, 211, 170, 57, 232, 47, 188, 11, 179, 70, 21, 245, 186, 71, 168, 2, 17, 0, 0, 0, 146, 74, 197, 170, 2, 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