Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce3d3e8a5b4e8a1fd33aee58ae7ab0f1d92e0cf5478e58e74b9ea7e30d5d25de

Tx prefix hash: 82fd3e52d96efaa60ac9a991659756f0b04a36ccf4445ef1cb699cf2721aa12f
Tx public key: ddffc2e31d81a2c79ce377e09b7f647bdc51df21e3ec13af4c5a327053e6315e
Timestamp: 1721788602 Timestamp [UCT]: 2024-07-24 02:36:42 Age [y:d:h:m:s]: 00:263:02:42:52
Block: 1072377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187971 RingCT/type: yes/0
Extra: 01ddffc2e31d81a2c79ce377e09b7f647bdc51df21e3ec13af4c5a327053e6315e021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6127eb2f883aa0ebb0aeed3e94dd3adf702b34adf9716bb8fc6fffbdb2d5008 0.600000000000 1544842 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": 1072387, "vin": [ { "gen": { "height": 1072377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6127eb2f883aa0ebb0aeed3e94dd3adf702b34adf9716bb8fc6fffbdb2d5008" } } ], "extra": [ 1, 221, 255, 194, 227, 29, 129, 162, 199, 156, 227, 119, 224, 155, 127, 100, 123, 220, 81, 223, 33, 227, 236, 19, 175, 76, 90, 50, 112, 83, 230, 49, 94, 2, 17, 0, 0, 0, 4, 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