Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e701855f465b6f6e34fd26fee5e8c99d3e4b38a4d436dd172a809f0b3cd19f5

Tx prefix hash: 2debcb17b0dff1214b47dce95b0b54a111a754460ae051fb3339d549289c6343
Tx public key: 29eff730b56f99eb51ed1ff72209b3360d7123f4b7264ee3baa6cae37cb24276
Timestamp: 1719929227 Timestamp [UCT]: 2024-07-02 14:07:07 Age [y:d:h:m:s]: 00:350:16:20:16
Block: 1056971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250499 RingCT/type: yes/0
Extra: 0129eff730b56f99eb51ed1ff72209b3360d7123f4b7264ee3baa6cae37cb242760211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32e72b16ac99598dbbaa17ffd22d47fe8ad5b20139f212c9ba3efc920a37e8bf 0.600000000000 1527400 of 15

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": 1056981, "vin": [ { "gen": { "height": 1056971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32e72b16ac99598dbbaa17ffd22d47fe8ad5b20139f212c9ba3efc920a37e8bf" } } ], "extra": [ 1, 41, 239, 247, 48, 181, 111, 153, 235, 81, 237, 31, 247, 34, 9, 179, 54, 13, 113, 35, 244, 183, 38, 78, 227, 186, 166, 202, 227, 124, 178, 66, 118, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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