Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd9c93271afc4c761c171ab085f7eef0634e6878491aaf885ab0409d9a93c131

Tx prefix hash: 95eefd11db0c4d59da013b50ed032c3bbeb2a1a393947282f7f717fbe25f12f1
Tx public key: 8e2dfe444b9434a62c4472d59fd36b8ed28615832524ede71c90f2c1d30e4ce1
Timestamp: 1590432093 Timestamp [UCT]: 2020-05-25 18:41:33 Age [y:d:h:m:s]: 05:163:14:30:06
Block: 103203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1301489 RingCT/type: yes/0
Extra: 018e2dfe444b9434a62c4472d59fd36b8ed28615832524ede71c90f2c1d30e4ce10211000001a62d7572bf000000000000000000

1 output(s) for total of 279.296706706000 dcy

stealth address amount amount idx
00: df074c7c790ff4117087dffd675503b12a0f1e8d38731e13ee796ca3e7fb23b8 279.296706706000 181088 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": 103213, "vin": [ { "gen": { "height": 103203 } } ], "vout": [ { "amount": 279296706706, "target": { "key": "df074c7c790ff4117087dffd675503b12a0f1e8d38731e13ee796ca3e7fb23b8" } } ], "extra": [ 1, 142, 45, 254, 68, 75, 148, 52, 166, 44, 68, 114, 213, 159, 211, 107, 142, 210, 134, 21, 131, 37, 36, 237, 231, 28, 144, 242, 193, 211, 14, 76, 225, 2, 17, 0, 0, 1, 166, 45, 117, 114, 191, 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