Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f51706616e3b6a9e39cc65de41fcc2405f454333e47f3a04aec7f6838520f5fd

Tx prefix hash: 2a3561f6077af46c80a507070fadffeeed8b9bff732ddf5cccd81d643dfbc728
Tx public key: 1e0193dd1ff30f22d6e776333d9aab10d831780afab073b3a73cdd0f1ca1aa73
Timestamp: 1721438982 Timestamp [UCT]: 2024-07-20 01:29:42 Age [y:d:h:m:s]: 00:259:07:32:24
Block: 1069522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185219 RingCT/type: yes/0
Extra: 011e0193dd1ff30f22d6e776333d9aab10d831780afab073b3a73cdd0f1ca1aa73021100000001162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 271f68f385f9c39702e312b9f5c5a35416d86e06d16a62a29fd820570f95edb4 0.600000000000 1540971 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": 1069532, "vin": [ { "gen": { "height": 1069522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "271f68f385f9c39702e312b9f5c5a35416d86e06d16a62a29fd820570f95edb4" } } ], "extra": [ 1, 30, 1, 147, 221, 31, 243, 15, 34, 214, 231, 118, 51, 61, 154, 171, 16, 216, 49, 120, 10, 250, 176, 115, 179, 167, 60, 221, 15, 28, 161, 170, 115, 2, 17, 0, 0, 0, 1, 22, 38, 19, 170, 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