Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6bff4d7a6c889c18b2c5f053bf991e0d3b9627e0af888238d7e61906cf92d65

Tx prefix hash: 2f27910440bb41b0703039849e36328f8cdc6b4b1ff7d2a86f827284e72259bd
Tx public key: 811fe6f30d78b6390b1978c9369ea70bc70c64cbf77d6b8795eb171dccb7a124
Timestamp: 1739522229 Timestamp [UCT]: 2025-02-14 08:37:09 Age [y:d:h:m:s]: 00:328:11:14:00
Block: 1218968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232587 RingCT/type: yes/0
Extra: 01811fe6f30d78b6390b1978c9369ea70bc70c64cbf77d6b8795eb171dccb7a1240211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32c69efd74b3f99f1158fddeda52654d2a888d2e713871ac2863e043e2b4f293 0.600000000000 1705789 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": 1218978, "vin": [ { "gen": { "height": 1218968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32c69efd74b3f99f1158fddeda52654d2a888d2e713871ac2863e043e2b4f293" } } ], "extra": [ 1, 129, 31, 230, 243, 13, 120, 182, 57, 11, 25, 120, 201, 54, 158, 167, 11, 199, 12, 100, 203, 247, 125, 107, 135, 149, 235, 23, 29, 204, 183, 161, 36, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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