Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de7f90cfa88e4b30c7dbc443822c978adc92aba932923def79cee675935f9a05

Tx prefix hash: c6a3fa0e9290df3c387df9ac56c82b10d9de5bb5fed752a5816e7165e7e0956a
Tx public key: 038ea2ec490b05ffca8d92c8893982323e4b61d7207303bf5816a96c4a521de2
Timestamp: 1716969815 Timestamp [UCT]: 2024-05-29 08:03:35 Age [y:d:h:m:s]: 00:155:16:39:44
Block: 1032438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111445 RingCT/type: yes/0
Extra: 01038ea2ec490b05ffca8d92c8893982323e4b61d7207303bf5816a96c4a521de202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdc9ff5c70102456c5ffbb9f1c19b08fe2dbe5f1db4952464ba804ad2c7e2a57 0.600000000000 1500891 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": 1032448, "vin": [ { "gen": { "height": 1032438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdc9ff5c70102456c5ffbb9f1c19b08fe2dbe5f1db4952464ba804ad2c7e2a57" } } ], "extra": [ 1, 3, 142, 162, 236, 73, 11, 5, 255, 202, 141, 146, 200, 137, 57, 130, 50, 62, 75, 97, 215, 32, 115, 3, 191, 88, 22, 169, 108, 74, 82, 29, 226, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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