Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45a9cc7dce751dededfd66ab51a6df9659c01938bb25d2d6dcb4c571eaf43132

Tx prefix hash: 7c85030bd1692747fffa380f3fd273ce414d092555e5a61a7c30416784ffe864
Tx public key: 43f097e0e2cc3f4162a6f17579cca6130e86a3e5b5431fac7ad55896f8453f54
Timestamp: 1715014715 Timestamp [UCT]: 2024-05-06 16:58:35 Age [y:d:h:m:s]: 01:184:06:32:52
Block: 1016228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390305 RingCT/type: yes/0
Extra: 0143f097e0e2cc3f4162a6f17579cca6130e86a3e5b5431fac7ad55896f8453f540211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 853cbd29b575aa2b8c0c01f7f58b20de0627ebd12d3b8a4fa0129dc8fe895934 0.600000000000 1479751 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": 1016238, "vin": [ { "gen": { "height": 1016228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "853cbd29b575aa2b8c0c01f7f58b20de0627ebd12d3b8a4fa0129dc8fe895934" } } ], "extra": [ 1, 67, 240, 151, 224, 226, 204, 63, 65, 98, 166, 241, 117, 121, 204, 166, 19, 14, 134, 163, 229, 181, 67, 31, 172, 122, 213, 88, 150, 248, 69, 63, 84, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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