Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0874761d86a717a5d06d89c753c210305f4ccf0fad1174fabeeae6fecefdb7a

Tx prefix hash: 7d7e4d63c0e925df282df424cae4abec60a0e8ec63182bcff31978c816e78122
Tx public key: 331b8ec3d76e516668f168daab77dc7198d22bcb1f24fbf32f7751482ca6828b
Timestamp: 1694898494 Timestamp [UCT]: 2023-09-16 21:08:14 Age [y:d:h:m:s]: 01:116:21:13:28
Block: 849635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344850 RingCT/type: yes/0
Extra: 01331b8ec3d76e516668f168daab77dc7198d22bcb1f24fbf32f7751482ca6828b02110000000433af99f4000000000000000000

1 output(s) for total of 0.939304930000 dcy

stealth address amount amount idx
00: 04fa707e2436ac6546f2d53e9e68eacae6d4e8108415c8162f59421f900980bf 0.939304930000 1303309 of 0

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": 849645, "vin": [ { "gen": { "height": 849635 } } ], "vout": [ { "amount": 939304930, "target": { "key": "04fa707e2436ac6546f2d53e9e68eacae6d4e8108415c8162f59421f900980bf" } } ], "extra": [ 1, 51, 27, 142, 195, 215, 110, 81, 102, 104, 241, 104, 218, 171, 119, 220, 113, 152, 210, 43, 203, 31, 36, 251, 243, 47, 119, 81, 72, 44, 166, 130, 139, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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