Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70a3c06db7947edcb9c0b3f712383f2306a2464aec9f956d2cbed3791306f4aa

Tx prefix hash: 995321ada189a94cf78aeb3913aa31a963fc3108478abb85d2145fad0d01f1f8
Tx public key: bf8bf4c71164c2fde2b6ae95109598abb1bd6fda234e40d75a2d6dbe2f7a324f
Timestamp: 1717294565 Timestamp [UCT]: 2024-06-02 02:16:05 Age [y:d:h:m:s]: 00:305:18:08:27
Block: 1035132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218507 RingCT/type: yes/0
Extra: 01bf8bf4c71164c2fde2b6ae95109598abb1bd6fda234e40d75a2d6dbe2f7a324f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06c9fb5e69e81fd5bd25df3a8976eb0612402bb025a5f7d9b2d694c003581d7b 0.600000000000 1503651 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": 1035142, "vin": [ { "gen": { "height": 1035132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c9fb5e69e81fd5bd25df3a8976eb0612402bb025a5f7d9b2d694c003581d7b" } } ], "extra": [ 1, 191, 139, 244, 199, 17, 100, 194, 253, 226, 182, 174, 149, 16, 149, 152, 171, 177, 189, 111, 218, 35, 78, 64, 215, 90, 45, 109, 190, 47, 122, 50, 79, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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