Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b90e882086656c9fd38f48863d0dff779ec5834a48bd7be1b421c150377f0c3e

Tx prefix hash: a4e5311c2471e659658200418b993bb4f7392e314b9cc524d80e184b89f27e3a
Tx public key: 070ee0d31a4a1170f291cfb2ad9b0861f1e8050ac996ec87bb42d06b0d223015
Timestamp: 1730078322 Timestamp [UCT]: 2024-10-28 01:18:42 Age [y:d:h:m:s]: 00:162:01:56:08
Block: 1141041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115652 RingCT/type: yes/0
Extra: 01070ee0d31a4a1170f291cfb2ad9b0861f1e8050ac996ec87bb42d06b0d223015021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb7e0d2551c001879c3fa1b067f72dfe589ad595a65ad945c5e8b6e73b9f3d9d 0.600000000000 1624848 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": 1141051, "vin": [ { "gen": { "height": 1141041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb7e0d2551c001879c3fa1b067f72dfe589ad595a65ad945c5e8b6e73b9f3d9d" } } ], "extra": [ 1, 7, 14, 224, 211, 26, 74, 17, 112, 242, 145, 207, 178, 173, 155, 8, 97, 241, 232, 5, 10, 201, 150, 236, 135, 187, 66, 208, 107, 13, 34, 48, 21, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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