Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f724183d5713f6550e6a3687b8fb4b17d0c74f114bdbb96b94eca03adb18adc6

Tx prefix hash: f229595242bfedbe819fa5fe4eec5ed99aa5943b274b7dc747d59955c2dc38c8
Tx public key: 6482446ede51aa21679a0681d02fcd07c210e5365623c875e5e3ac6f8fa985f9
Timestamp: 1702710805 Timestamp [UCT]: 2023-12-16 07:13:25 Age [y:d:h:m:s]: 01:035:13:27:37
Block: 914216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286735 RingCT/type: yes/0
Extra: 016482446ede51aa21679a0681d02fcd07c210e5365623c875e5e3ac6f8fa985f9021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38eb596fb7c2d72d3c29490f2c8c2e586dfd4fb8e51c8b36c8ddc21205603af4 0.600000000000 1371502 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": 914226, "vin": [ { "gen": { "height": 914216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38eb596fb7c2d72d3c29490f2c8c2e586dfd4fb8e51c8b36c8ddc21205603af4" } } ], "extra": [ 1, 100, 130, 68, 110, 222, 81, 170, 33, 103, 154, 6, 129, 208, 47, 205, 7, 194, 16, 229, 54, 86, 35, 200, 117, 229, 227, 172, 111, 143, 169, 133, 249, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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