Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5c1371ac5d439adbcf45b05671746ca95f3b891046304f6f1ad064d3d631336

Tx prefix hash: 31405de3cb46d4a32ddb051bcf2d6dbaab12018ea65adc34c128ce56a2fcffa2
Tx public key: 6b059510565a714d84e72290e2fb988c519829bd4d6b96973ba341b6e033f818
Timestamp: 1743752139 Timestamp [UCT]: 2025-04-04 07:35:39 Age [y:d:h:m:s]: 00:304:01:35:08
Block: 1253976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214968 RingCT/type: yes/0
Extra: 016b059510565a714d84e72290e2fb988c519829bd4d6b96973ba341b6e033f8180211000000024060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5c65868adfff6ec38ec864f97fa6a96e94ff9a98e2196dcc54dc28bb40f893e 0.600000000000 1741057 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": 1253986, "vin": [ { "gen": { "height": 1253976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5c65868adfff6ec38ec864f97fa6a96e94ff9a98e2196dcc54dc28bb40f893e" } } ], "extra": [ 1, 107, 5, 149, 16, 86, 90, 113, 77, 132, 231, 34, 144, 226, 251, 152, 140, 81, 152, 41, 189, 77, 107, 150, 151, 59, 163, 65, 182, 224, 51, 248, 24, 2, 17, 0, 0, 0, 2, 64, 96, 246, 210, 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