Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dd29177f8889a69c7fe062c2b6975ddbf983b2086b5514356b55319cfb4b8ee

Tx prefix hash: ea72ada406cee93686e213e1ffb3a8b36c81d7f3b374f1084b35101f32d56eb9
Tx public key: fee8d91b48f620f52e468545af485f6ec9875b883a031045224f03450353df0d
Timestamp: 1686509639 Timestamp [UCT]: 2023-06-11 18:53:59 Age [y:d:h:m:s]: 02:148:06:56:54
Block: 780169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 625712 RingCT/type: yes/0
Extra: 01fee8d91b48f620f52e468545af485f6ec9875b883a031045224f03450353df0d02110000000333af99f4000000000000000000

1 output(s) for total of 1.595792422000 dcy

stealth address amount amount idx
00: 3903e3baf1f62a8d32e3b6a07e7af625f9d18db5a45af6d7ef31660b551b0fb5 1.595792422000 1229868 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": 780179, "vin": [ { "gen": { "height": 780169 } } ], "vout": [ { "amount": 1595792422, "target": { "key": "3903e3baf1f62a8d32e3b6a07e7af625f9d18db5a45af6d7ef31660b551b0fb5" } } ], "extra": [ 1, 254, 232, 217, 27, 72, 246, 32, 245, 46, 70, 133, 69, 175, 72, 95, 110, 201, 135, 91, 136, 58, 3, 16, 69, 34, 79, 3, 69, 3, 83, 223, 13, 2, 17, 0, 0, 0, 3, 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