Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acd8e07b6559aed33ff09c3582b72826609cb1674a1d18d86c95be76037b154a

Tx prefix hash: 49bd2956a4d97ad3699ee9b723f307fdf60be9d9e2d0b7f2bcc89ceefd7a4f9a
Tx public key: e84507969e1ec8dc85ccd7e213f60f2607acc7a0837810c82c8022857dd81772
Timestamp: 1706921318 Timestamp [UCT]: 2024-02-03 00:48:38 Age [y:d:h:m:s]: 01:027:06:38:19
Block: 949114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280536 RingCT/type: yes/0
Extra: 01e84507969e1ec8dc85ccd7e213f60f2607acc7a0837810c82c8022857dd8177202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d46fce6c7006dfe1fcf364644375defffae101d89c6a1ca3a2ce3b361fd3ce9e 0.600000000000 1407636 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": 949124, "vin": [ { "gen": { "height": 949114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d46fce6c7006dfe1fcf364644375defffae101d89c6a1ca3a2ce3b361fd3ce9e" } } ], "extra": [ 1, 232, 69, 7, 150, 158, 30, 200, 220, 133, 204, 215, 226, 19, 246, 15, 38, 7, 172, 199, 160, 131, 120, 16, 200, 44, 128, 34, 133, 125, 216, 23, 114, 2, 17, 0, 0, 0, 5, 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