Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ae9704fb667ac42c7dacb41d59b7687e8ddbbef1efaf34b1d1752828cb4edc7

Tx prefix hash: 13c5f772b83ac16406e4dee67b8bf60ed6eb84cb5c33380c2a2e0c9e5c99b8c2
Tx public key: afcc8e283f6febb433ec0593b314b9a8e075bf3c3efbfd537df3cf7118484e74
Timestamp: 1722084631 Timestamp [UCT]: 2024-07-27 12:50:31 Age [y:d:h:m:s]: 00:302:02:35:01
Block: 1074843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215860 RingCT/type: yes/0
Extra: 01afcc8e283f6febb433ec0593b314b9a8e075bf3c3efbfd537df3cf7118484e74021100000028e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfb5e1ec17da1feebf644c6c2d6e823cb4ddea28cb30e895334852ee6b378d2a 0.600000000000 1547362 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": 1074853, "vin": [ { "gen": { "height": 1074843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfb5e1ec17da1feebf644c6c2d6e823cb4ddea28cb30e895334852ee6b378d2a" } } ], "extra": [ 1, 175, 204, 142, 40, 63, 111, 235, 180, 51, 236, 5, 147, 179, 20, 185, 168, 224, 117, 191, 60, 62, 251, 253, 83, 125, 243, 207, 113, 24, 72, 78, 116, 2, 17, 0, 0, 0, 40, 233, 20, 221, 21, 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