Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58d32f839c77c9c35f4cdde709ad53d756d5e1cc1b7a6f0e17a31861f7ced24c

Tx prefix hash: 755038103773d2d9028a38c368a6343fe35f4d962ffadc88a91a296cd2249eb3
Tx public key: aa26aaa2197c25fed0a1b33cbcc23ef28ae9a68644ce74e1d25c41c8ce33d2a6
Timestamp: 1705281725 Timestamp [UCT]: 2024-01-15 01:22:05 Age [y:d:h:m:s]: 01:082:23:17:50
Block: 935499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320409 RingCT/type: yes/0
Extra: 01aa26aaa2197c25fed0a1b33cbcc23ef28ae9a68644ce74e1d25c41c8ce33d2a602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc1dbb7654e09b071af3dd77f3a0efd259be67f425e74ff3be9103e34a113508 0.600000000000 1393515 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": 935509, "vin": [ { "gen": { "height": 935499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc1dbb7654e09b071af3dd77f3a0efd259be67f425e74ff3be9103e34a113508" } } ], "extra": [ 1, 170, 38, 170, 162, 25, 124, 37, 254, 208, 161, 179, 60, 188, 194, 62, 242, 138, 233, 166, 134, 68, 206, 116, 225, 210, 92, 65, 200, 206, 51, 210, 166, 2, 17, 0, 0, 0, 1, 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