Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81b7375377231989befc1023fd1bc5045e0a0890510b772540517c2fa449c506

Tx prefix hash: fda5b70952ca4fea9406154840d53d9759a695e15f058c5529a691f19e42fe8e
Tx public key: 392fc074d9670deab7c226e30c2481693f7c123fc0b7f6cafe8c5215222d3f4e
Timestamp: 1717330905 Timestamp [UCT]: 2024-06-02 12:21:45 Age [y:d:h:m:s]: 01:160:23:58:47
Block: 1035437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373638 RingCT/type: yes/0
Extra: 01392fc074d9670deab7c226e30c2481693f7c123fc0b7f6cafe8c5215222d3f4e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e878b3716d0e9bcde5954a579a8db7173812cb1f6bbc1c0cfd0eafe3ee8c341 0.600000000000 1503958 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": 1035447, "vin": [ { "gen": { "height": 1035437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e878b3716d0e9bcde5954a579a8db7173812cb1f6bbc1c0cfd0eafe3ee8c341" } } ], "extra": [ 1, 57, 47, 192, 116, 217, 103, 13, 234, 183, 194, 38, 227, 12, 36, 129, 105, 63, 124, 18, 63, 192, 183, 246, 202, 254, 140, 82, 21, 34, 45, 63, 78, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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