Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e0783aa4ba7a4def4b7eb499f85c263c8e0c19a2f626df1739a1d321866f6c3

Tx prefix hash: d42661f2d94b8e7ae89e6aae102d945bd28705285ef2132bd8ac987e1c59a3da
Tx public key: 010ec19a9edbef0c373ddb2b021aa467cc9e180958920dd59c98e510b6398c24
Timestamp: 1581993177 Timestamp [UCT]: 2020-02-18 02:32:57 Age [y:d:h:m:s]: 05:015:17:11:51
Block: 67130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164321 RingCT/type: yes/0
Extra: 01010ec19a9edbef0c373ddb2b021aa467cc9e180958920dd59c98e510b6398c2402110000000103d36d11000000000000000000

1 output(s) for total of 367.765724534000 dcy

stealth address amount amount idx
00: 22f4a1b6495d427e4aa6e90f6c43b34f5bc286d8e50bcaec40fa60c5596af1a2 367.765724534000 123684 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": 67140, "vin": [ { "gen": { "height": 67130 } } ], "vout": [ { "amount": 367765724534, "target": { "key": "22f4a1b6495d427e4aa6e90f6c43b34f5bc286d8e50bcaec40fa60c5596af1a2" } } ], "extra": [ 1, 1, 14, 193, 154, 158, 219, 239, 12, 55, 61, 219, 43, 2, 26, 164, 103, 204, 158, 24, 9, 88, 146, 13, 213, 156, 152, 229, 16, 182, 57, 140, 36, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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