Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8df1a5058be803e025c81c9534c108ff505d18b0217fd6cf57cb360ad93b256b

Tx prefix hash: c65ac4398d87cde5fc91b822c184c9587e257b5e47b8d8b91e42355a0f56cbad
Tx public key: 4f34c09f03cde997b47c14405bcc390116ae4091e3c4a7fbe1e3dda4fc77091d
Timestamp: 1723710953 Timestamp [UCT]: 2024-08-15 08:35:53 Age [y:d:h:m:s]: 00:245:03:08:43
Block: 1088331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175067 RingCT/type: yes/0
Extra: 014f34c09f03cde997b47c14405bcc390116ae4091e3c4a7fbe1e3dda4fc77091d02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c58514a31edc76a1afc102599920ea44e03a08a52b42cf10b95fc5dd0ba8141 0.600000000000 1562946 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": 1088341, "vin": [ { "gen": { "height": 1088331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c58514a31edc76a1afc102599920ea44e03a08a52b42cf10b95fc5dd0ba8141" } } ], "extra": [ 1, 79, 52, 192, 159, 3, 205, 233, 151, 180, 124, 20, 64, 91, 204, 57, 1, 22, 174, 64, 145, 227, 196, 167, 251, 225, 227, 221, 164, 252, 119, 9, 29, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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